> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-content-administration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salsa-digital.gitbook.io/govcms-content-administration/roles-and-permissions/common-roles.md).

# Common roles

Drupal websites use role‑based permissions to ensure publishing quality and to protect website stability.

GovCMS comes with the following roles out-of-the-box:

* **Content Author:** A Content Author can typically create new content, make content revisions and mark them for review by a Content Approver.
* **Content Approver:** A Content Approver can publish, archive and delete content created by Content Editors.
* **Site Administrator:** A Site Administrator can delete content, revert content revisions, place content blocks and perform other content management tasks that require special caution and experience.

However, your developers can customise these roles and permissions as needed.

### Why multiple roles?

GovCMS’ different roles are set up to restrict permissions around who can edit and approve content and who can make administrative changes to the website.

However, you can apply multiple roles to a single user.

By assigning a user both the **Content Author** and **Content Approver** role, they will be able to edit and approve content to be published.

### Customising roles

While only the above roles are provided out-of-the-box, your developers can create custom roles specifically for your website, and restrict permissions to create more granular control.

For example:

* You could create a Legal Review role with an additional permission to moderate content through the Legal Review state.
* You could create a role that only has access to create and edit content of a certain type, for example an event content type. This would give them full control over all events on the website without the permission to accidentally alter any publications or page content.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://salsa-digital.gitbook.io/govcms-content-administration/roles-and-permissions/common-roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.