Add docs about permissions and webmaster libraries #1827
Conversation
| * Has access to the same as editor plus the site's configuration | ||
| options in /admin/config, user creation in /admin/people, and | ||
| changing the site's appearance in /admin/appearance. | ||
| * This is the role assigned to trusted users on regular libraries. |
There was a problem hiding this comment.
| * This is the role assigned to trusted users on regular libraries. | |
| * This is the role assigned to trusted users on Editor libraries. |
Please consider referring to the name of the plan used by the business and elsewhere in the docs.
The name overlaps with the user role but in practice I do not think this has been a problem.
| @@ -0,0 +1,31 @@ | |||
| # Permissions and roles | |||
|
|
|||
| 'mediator': | |||
There was a problem hiding this comment.
| 'mediator': | |
| ## `mediator`: |
Just a suggestion to use headlines as this seems to be what it is. Take it or leave it 😄
| # Webmaster libraries | ||
|
|
||
| Libraries on the "webmaster" plan has extended permissions compared to | ||
| regular libraries. They have access to most of the Drupal | ||
| administration pages, and can install custom modules. | ||
|
|
||
| See [Permissions and roles](./permissions-and-roles) for details on | ||
| Drupal setup. | ||
|
|
||
| In addition to the Drupal setup, the site should use the `webmaster` | ||
| plan when configured in [DPL | ||
| Platform](https://danskernesdigitalebibliotek.github.io/dpl-docs/DPL-Platform/), | ||
| this creates a `moduletest` environment for testing and implies a | ||
| slightly different deployment scheduling. |
There was a problem hiding this comment.
👍 I appreciate this addition. Consider moving it to dpl-docs.
As I see it the plan handling is handled partly by the CMS and partly with the Platform. Now what we have a general location within the documentation I think this would be a nice place to put this information and then refer to the parts within the individual projects.
With this in mind I also think it would make sense to provide an overview of all the plan types a bit like we have done elsewhere instead of only mentioning the webmaster libraries.
Just some doc updates.