> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/administration/role-management.md).

# Role Management

## Purpose

Define and maintain role-based permissions for Messaging Portal modules.

## Who this is for

Administrators who govern access to Communication, Planning, Construction, Analysis, Administration, and Technology areas.

## Prerequisites

* Administrator access to Role Management.
* Organizational policy defining who may configure channels versus execute campaigns.

{% hint style="info" %}
For a short onboarding summary of role types, see [Create and manage roles](broken://pages/JjjojIyKxaiBPzzLwvtg). This page describes operational permission scope in the portal.
{% endhint %}

## Common roles

| Role              | Typical portal scope                                                                                                                        |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **Agent**         | Execute day-to-day messaging: Communication, Planning (read/use), Construction (use templates/links), Analysis (view history as permitted). |
| **Supervisor**    | Agent capabilities plus broader Analysis, campaign oversight, and selected Administration tasks (as enabled by your tenant).                |
| **Administrator** | Full Administration: sources, phones, bots, source theme, users, roles, settings, and Technology onboarding.                                |

<figure><img src="https://3261478287-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXHkoH2WwcemdqskPI0KI%2Fuploads%2FBNumQLJm6ZzTsrZloQZX%2Fimage.png?alt=media&amp;token=8999c339-6a3d-49e3-b88d-f05014c8c7fa" alt=""><figcaption><p>Roles management</p></figcaption></figure>

## Module permission matrix

Use this matrix when assigning or auditing roles. Exact toggles depend on your tenant configuration.

| Module         | Agent               | Supervisor           | Administrator |
| -------------- | ------------------- | -------------------- | ------------- |
| Communication  | Send (if enabled)   | Send + oversee       | Full          |
| Planning       | Use groups/contacts | Manage audiences     | Full          |
| Construction   | Use templates/links | Create/manage assets | Full          |
| Analysis       | View (scoped)       | View + export        | Full          |
| Technology     | —                   | View (optional)      | Full          |
| Administration | —                   | Partial (optional)   | Full          |
| Settings       | —                   | —                    | Full          |

## Steps

1. Open **Administration** and go to **Role Management**.
2. Review existing role profiles and their module permissions.
3. Create or edit a role to match organizational policy.
4. Assign the role to users in [User Management](/syntphony-messaging-portal/messaging-tools/administration/user-management.md).
5. Validate access with a test user before production rollout.

## Expected outcome

Access is controlled by role, reducing configuration risk and improving governance.

## Related pages

* [Administration](/syntphony-messaging-portal/messaging-tools/administration.md)
* [User Management](/syntphony-messaging-portal/messaging-tools/administration/user-management.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/administration/role-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.