> 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/introduction-to-govcms/overview-of-user-roles.md).

# Overview of user roles

In GovCMS (and most CMSs) there are different ‘roles’ for different users with different ‘permissions’. This simply means that different roles can perform different functions.

### GovCMS roles

GovCMS uses the following roles:

* **Content Editor** - A Content Editor can typically create new content and content revisions and mark them for review by an 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.

### Why multiple roles?

GovCMS’s different roles are set up to restrict:

* Who can create, edit and delete content
* Who can publish or archive content
* Who can perform more technical tasks that will have larger effects on the website and CMS, such as adding metadata, adding content fields to content types, adding new menu items, etc.


---

# 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/introduction-to-govcms/overview-of-user-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.