> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/news/news-roles-permissions.md).

# Roles and permissions in News

### The roles of the News application

#### Global administrator

* Assign the role of **Communicator** to employees
* Access all administration features

#### Communicator

* Manage **all sections** of the organization (create, edit, delete)
* Edit the contributors and audience of the sections
* View publication statistics (views, likes, comments)
* Manage scheduled and pinned publications
* Prepare and share drafts

#### Contributor

* Create posts **only in the sections assigned to them**
* Manage their own publications (edit, delete)

#### Collaborator

* View publications in the sections whose audience they are part of
* Like and comment on publications (if enabled)
* Vote in polls

### Publication rights management

The administrator can configure publication rights from **Administration** > **Settings** of the News application:

* Who can manage sections
* Access to Inspirations (publication ideas library)
* Alert frequency

### What the assistant can do

The assistant cannot directly modify News roles. It can explain how permissions work and guide users to the administration pages.


---

# 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://help.steeple.com/en/news/news-roles-permissions.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.
