User rights v2

[Gustry]

Mainly include and superseeds #237

Compare to #237 :

• remove pictures which were not used
• review sentences and RST syntax

What is still in #237 is the example which needs to be reviewed and added in the doc.

[Gustry]

First review done by @mdouchin, he approves

Screenshot not updated

[nworr]

The lizmap plugin section is a bit out of context here.

I think we may need to create a section describing all rights , their "scope" (project, repository), and where their can be set.

[Gustry]

The lizmap plugin section is a bit out of context here.

I was wondering where I should add this info, which is important IMHO.

These settings are hidden, because it's a kind of rights, but set in the plugin itself, not in the main WEB admin interface.
Keen to have feedbacks.

During a training, I more or less present hiding project/layers/features like a funnel.

1. at the repository level
2. at the project level
3. (at the tool level)
4. at the layer's feature level

I think we may need to create a section describing all rights , their "scope" (project, repository)

I would prefer having tooltips, or a new column in the table, in the web, so we don't need to maintain a list in RST.
Modules are introducing their own rights and grousp, like Cadastre, MapBuilder etc