> For the complete documentation index, see [llms.txt](https://everyday-digital.gitbook.io/account-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://everyday-digital.gitbook.io/account-docs/guides/manage-team-roles-and-permissions.md).

# Manage Team: Roles & Permissions

## **What is a Team?**

**Your team consists of platform users.** You can set team users that need to have access to your account to perform various roles.

## What are the Team User Roles?

**A user can have one or more User Roles, and permissions can be adjusted as needed.** Customise the default permissions for each role by allowing or denying access to each available feature.

### Agent Role

**The Agent has full access - this is the master role.** An account only has one Agent. The Agent can add new users, create groups, and create workflows. Only the Agent can reassign the Agent role.

### **Admin Role**

**The Admin has full access.** Admins can add new team members, create groups and create workflows. It is recommended to always have two Admin roles.

### Support Role

**The Support Role has access to** [**support tickets**](broken://pages/TROcJPO7W0R5eifZDHMZ) submitted on [Resolve](https://everyday-digital.gitbook.io/resolve-docs/) from other team members and, where applicable, from linked accounts. The Support Contact can also escalate issues to the [Platform Operator](broken://pages/wytD7om4EuNpC0cyIYzd#platform-operator) via [Resolve](https://everyday-digital.gitbook.io/resolve-docs/).

### **Publisher Role**

**The Publisher has limited access.** The Publisher role can author & publish content, but can't manage users & groups.

### Analytics Role

**The Analyser only has access to analytics.** &#x20;

### **Data Privacy Role**

**The Data Privacy role only has enough access to do data privacy checks.** This role only has access to Analytics, Groups, and Data Compliance.

{% hint style="info" %}
**Team or Access?** Users are either part of your internal team, or they are external users who have been given [access to your account](/account-docs/guides/account-access.md). When adding either a Team User or an [Access User](/account-docs/guides/account-access.md), you can choose their role and set their access permissions.
{% endhint %}

## User Role Permissions

| Feature                | Agent | Admin   | Support | Publisher | Analyser |
| ---------------------- | ----- | ------- | ------- | --------- | -------- |
| **Authoring**          | Yes   | Yes     | Yes     | Yes       | No       |
| **Analytics & Trends** | Ye    | Yes     | Yes     | Yes       | Yes      |
| **Marketplace**        | Yes   | Yes     | Yes     | Yes       | Yes      |
| **Groups**             | Yes   | Yes     | Yes     | No        | No       |
| **Account & Access**   | Yes   | Limited | Yes     | No        | No       |
| **Cloudfile**          | Yes   | Yes     | No      | Yes       | No       |

## How to add and invite Team Users

1. **From the menu, select Account & Access.** Select the + icon (bottom right).
2. **Enter the User's details, then select a** [**user role**](/account-docs/guides/manage-team-roles-and-permissions.md#user-role-types)**.** Each role comes with default permissions. You can customise individual permissions, as needed.
3. **Set up Access Limits.** You can limit access to the available features, as required. By default, the user will have access to all.
4. **Invite the user.** Select the Invite button. The user will be sent an account activation email.&#x20;
5. **Track the Team Member's account status by referring to the State column.** Invites can have the following states: Notified, Active, or Expired. If expired, the invite can be resent.

   After the user has activated their account, they will receive an email with instructions on how to access the app.

## What can Team Users do?

* access account and platform features assigned to them;
* use their credentials to log in to the platform account;
* switch between the accounts they have access to;
* collaborate with fellow users.
