check user permissions using "permissions" field

[alexbruy]

As described in MerginMaps/qgis-plugin#351 when user who is not an owner of the organization tries to sync project of the organization they get error. It happens because client relies on the access field of the project information to determine whether user has write permissions on a given project. However access field is taken from the explicit project permissions, while invited to the organization users get access via this organization.

In order to overcome this issue we need to check write access using permissions field, as this field is evaluated with respect to namespace.

Refs MerginMaps/qgis-plugin#351

Refs CU-28km50n

[alexbruy]

@varmar05 hope I understand your explanations correctly. But it looks like both fields "writersnames" and "permissions" should be taken into account, as project can be shared between users directly without organization.

[saberraz]

That's correct:
1- you can be a part of an organisation with write access.
2- you can be also outside an organisation and the project is shared with you with write permission

[varmar05]

@varmar05 hope I understand your explanations correctly. But it looks like both fields "writersnames" and "permissions" should be taken into account, as project can be shared between users directly without organization.

field "permissions" should be enough to cover both use cases since it check for direct permissions and org permissions

[ghost]

Task linked: CU-28km4we Can't remove project with 'remove locally' option

[varmar05]

@alexbruy do we have tests for both use cases? sharing directly and via organization?