> ## Documentation Index
> Fetch the complete documentation index at: https://docs.caplena.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Understanding Role-Based Permissions

> This guide walks you through how to assign and update roles, and what each role allows.

## Managing User Roles in Caplena

Assigning the right role is key to giving team members the access they need. In Caplena, roles define what a user can do across all projects and reports.

## How to Change a User’s Role

Changing roles is simple and takes less than a minute:

**Step 1**

Go to your **Account page**

**Step 2**

Open the **Team** section

**Step 3**

Find the user whose role you want to change

**Step 4**

Use the dropdown menu to select a new role

[Loom video player](https://www.loom.com/embed/4a224d0715f14cbd9751a02d7d29a811)

## Role Overview

Here’s a breakdown of the six user roles available:

### External Topic Assignment

> [!TIP]
>
> *Best for external partners or freelancers who should only work on their own content.*

No upload capability; No access to projects or dashboards of others by default.

### Administrator

> [!TIP]
>
> *Best for power users who manage subscriptions, teams, and integrations across the platform.*

Access to the projects, questions and reports of all users; Team and subscription management permissions.

### Full Data Access

> [!TIP]
>
> *Best for senior team members who need access to all projects and reports without admin responsibilities.*

Upload capability; Access to projects & dashboards of all team members.

### Project Manager

> [!TIP]
>
> *Best for team leads who manage their own projects but don’t require access to others’ work.*

Upload capability; Only full access to projects created by oneself, but access to all topic collections and fine-tuned AIs from all team members.

### Internal Analyst

> [!TIP]
>
> *Best for team members working across projects, without needing downloads or reports.*

No upload capability; Permission to edit and access projects of all team members, but no permission to download projects and no access to reports of others.

### Analyst

> [!TIP]
>
> *Best for stakeholders or junior team members who only need to view and explore results.*

Permission to view and visualize projects of all team members, but no permission to edit or download any projects.

## Removing a User

When you no longer need a team member's account — for example, a temporary contractor whose contract has ended — you can remove them from **Account → Team**.

**1. Open the Team section**

Go to your **Account page** and open the **Team** section.

**2. Remove the user**

Find the user you want to remove and select the option to delete their account.

**3. Choose what happens to their assets**

A confirmation dialog asks you to choose one of two options:

* **Transfer all the user's assets (Projects, reports & alerts) to the root user, before deleting the account** — recommended in almost all cases. Nothing is lost; ownership simply moves to the account's root user.
* **Do NOT transfer the user's assets, but delete them along with the account itself** — permanently deletes the user's projects, reports, and alerts along with their account. This cannot be undone.

**4. Confirm**

Type the user's first name into the confirmation field and click **Delete**.

> [!WARNING]
>
> This action cannot be undone. If you choose not to transfer the user's assets, their projects, reports, and alerts are permanently deleted along with the account.

> [!TIP]
>
> If you're removing a user only to free up a seat temporarily (e.g. while someone is on leave), transferring their assets to the root user first means you can safely re-invite them later without having lost anything — though their projects and reports will need to be reassigned back to them manually.

## Credit Usage Permission

The **Credit Usage** permission determines whether a user can perform operations that consume credits in Caplena.

### Operations requiring credits

* AI-assisted coding
* Topic generation
* AI topic assignment
* Other machine learning operations

### Roles with Credit Usage permission

| Role | Credit Usage |
| :- | :- |
| Administrator | ✓ |
| Full Data Access | ✓ |
| Project Manager | ✓ |
| Internal Analyst | ✗ |
| External Topic Assignment | ✗ |
| Analyst | ✗ |

### What happens without Credit Usage permission

If a user without **Credit Usage** permission attempts an operation that consumes credits, they will see an error message indicating that they need to contact their organization administrator to enable the permission.

## Sensitive Columns Permission

Columns marked as **Sensitive** (available on auxiliary columns) hide their data from users who don't have the right permission — useful for excluding personally identifying or otherwise restricted information from view.

Only users with the **View Sensitive Columns** permission can:

* See the Sensitive toggle on a column
* See sensitive column data within project data
* Export sensitive columns

### Roles with View Sensitive Columns permission

| Role | View Sensitive Columns |
| :- | :- |
| Administrator | ✓ |
| Full Data Access | ✓ |
| Project Manager | ✗ |
| Internal Analyst | ✗ |
| External Topic Assignment | ✗ |
| Analyst | ✗ |

> [!NOTE]
>
> This is the **default by role**. An Admin or user with Full Data Access can also grant **View Sensitive Columns** to a specific user on a specific project — for example, giving a Project Manager visibility into sensitive columns on just one project without changing their role. See [Object-Level Permissions](https://docs.caplena.com/settings-administration/permissions-deep-dive/object-level-permissions.md) for how to grant a per-project override.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.