User management in Qfield while creating project through field tm

[manjitapandey]

Is your feature request related to a problem? Please describe.
Currently, When a QGIS project is created through field tm, the user will not be upgraded to manager and won't be able to access features like submissions and managerial aspects.

Describe the solution you'd like
While creating project, we can ask user to input their Qfield cloud email address or username. We can provide a description saying they should have Qfield cloud account and prompt them to Qfield cloud for account creation. (since this step is easy enough, we should opt for this way instead of creating new user ourselves). Then during project creation on Qfield, we can update the role of that user to manager so they get all access of that projects.
Also we will not be creating members since, all projects in Qfield are by default public projects which will be visible for mapping by all users.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
@spwoodcock please add anything if you have any more thoughts around it.

[linear]

TECH-908

[spwoodcock]

An important consideration.

For mappers:

• To start we can add a single service user account, similar to the single appuser token we have for ODK.

• The user will have to enter the generic shared account details in the QField app.

• The account will be scoped to only access a single project, for security. With edit capabilities, but not project management.

• The credentials are shown on the project details page, plus a QRCode for easier usage (will configure the project id and username automatically).

For managers:

• A second account is made with project management permissions during project creation.

• The user/pass credentials are provided only once, and the manager is asked to save them.

• They can log into QFieldCloud or QGIS plugin and edit as they wish.

Future plans

• To link individual users and OSM attribution, we need to create a QFC user for each logged in FieldTM user.

• The user should then be able to log into QFC via OSM OAuth integration.

[manjitapandey]

The user will have to enter the generic shared account details in the QField app.

Users in Qfield mostly have their own Qfield credentials. If we create another account for them, It could confuse mappers. Also on most of the cases, logging in by scanning QR code is not functional on most mobile devices which may be issue on practical use.

The account will be scoped to only access a single project, for security.

Do we provide project level permission to the users? Also what is the need for this because the qfield projects are public by default meaning everyone has access to contribute to the project. Doesn't this role restriction code complicates the codebase?

[spwoodcock]

The user will have to enter the generic shared account details in the QField app.

Users in Qfield mostly have their own Qfield credentials. If we create another account for them, It could confuse mappers. Also on most of the cases, logging in by scanning QR code is not functional on most mobile devices which may be issue on practical use.

The account will be scoped to only access a single project, for security.

Do we provide project level permission to the users? Also what is the need for this because the qfield projects are public by default meaning everyone has access to contribute to the project. Doesn't this role restriction code complicates the codebase?

Yep you are right, we can have mixed usage.
We should offer the ability to either use your own login OR use the provided service account.

Option 1: "Use my own account"
Option 2: "Use a generic FieldTM account"

For QRCode scanning including project configuration and login, you need QField v4 (recently released).

For QField, a public project allows for public viewing, but not public contribution (correct me if I am wrong and testing shows this is different). So we need a account to be made with the lowest permission required to add data.

[spwoodcock]

User management implemented via Field-TM UI instead.