Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add @mm_project_role QGIS variable for the current user's project role

Open
#4,648 1 comment 0 reactions 1 assignee View on GitHub

@xkello is already working on this.

Since Sep 21, 2026.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
cpp
Domain
mobile-dev

Research direction

Start by tracing the existing mm_* variables in the mobile app and checking the plugin's displayed project-role values. Review the expression and form-default integration plus offline and sync handling; done means @mm_project_role returns the matching role, is empty in the stated inactive cases, and produces the same result in QGIS and the field.

Written by the indexing model from the issue text.

Description

enhancement forms

Current situation

The current user's role on a project isn't reachable from expressions, so authors can't set up expression-based behaviour that depends on the user's role.

What we want

A new Mergin variable, @mm_project_role, returning the current user's role on the active project, usable in expressions and form default values (like the other mm_* variables in the mobile app).

Expected behavior (user's view)

  • Returns the user's role on the open project as text.
  • Works offline and stays correct after syncing.
  • Empty when signed out or the project isn't a Mergin project.

The same expression must give the same result in QGIS and in the field, so the variable name and role values need to match the plugin exactly.

Role values users will see are reader, editor, writer, owner. Should mirror what the app already shows for roles.

Dominant language
C++
Stars
388
Forks
87
Avg merge
4d 1h
Merged PRs (30d)
23

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/mobile

All issues in MerginMaps/mobile

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.