> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://docs.intractive.app/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Users

# Inviting team members and managing roles
This article explains how to give people access to your Intractive account and what each role (**Admin**, **Editor**, **Viewer**) is allowed to do.
## How access works: three levels, three roles
Before you start inviting, it helps to know how access is built up. Intractive has **three levels**, nested inside each other:
**Organization → Project → Story → content blocks**

Access flows **down, never up**. Someone who is an **Admin** on the whole organization is automatically an Admin on every project and every story inside it. Someone who only has a role in a single story has access to *that* story alone, nothing above it.
Every organization, project and story also has an **Owner**, usually whoever created the account. The Owner has the same rights as an Admin and is marked with an **Owner** label in the member list.

Here's what each role can do:
| **Role** | **What they can do** |
| ---- | ---- |
| **Admin** | Full control at their level and everything beneath it: edit settings, |
| **Editor** | Create and edit content — stories, branches and new releases |
| **Viewer** | Read-only. Browse projects and stories and view analytics, reviews and sessions, without making any changes. |

| 💡 Good to know: at organization level, Editors can also manage shared articles, article groups and tags. Viewer is the safest, least-permissive role — so it's the default whenever you invite someone.

## **Quick reference: what each role can do**
Per level, the table below summarises the most common actions. “✅” = allowed, “—” = not allowed.

### **Organization**
| Action | Admin | Editor | Viewer |
| ---- | ---- | ---- | ---- |
| View Organization | ✅ | ✅ | ✅ |
| Edit Organization profile | ✅ | ✅ | — |
| Create a new Project | ✅ | — | — |
| Invite team members | ✅ | — | — |
| Change member roles | ✅ | — | — |
| Manage shared articles / videos | ✅ | ✅ | — |
| View all Projects & Stories | ✅ | ✅ | ✅ |

### **Project**
| Action | Admin | Editor | Viewer |
| ---- | ---- | ---- | ---- |
| View Project | ✅ | ✅ | ✅ |
| Edit Project settings | ✅ | — | — |
| Create a Story | ✅ | — | — |
| Delete a Story | ✅ | — | — |
| Duplicate / paste Stories | ✅ | — | — |
| Edit Stories inside Project | ✅ | ✅ | — |
| Sort Stories | ✅ | ✅ | — |
| View analytics & sessions | ✅ | ✅ | ✅ |
| Invite to Project | ✅ | — | — |
| Delete Project | ✅ | — | — |

### **Story**
| Action | Admin | Editor | Viewer |
| ---- | ---- | ---- | ---- |
| View Story | ✅ | ✅ | ✅ |
| Edit Story content | ✅ | ✅ | — |
| Create a release | ✅ | ✅ | — |
| Delete a release | ✅ | — | — |
| Duplicate Story | ✅ | — | — |
| Delete Story | ✅ | — | — |
| View analytics & reviews | ✅ | ✅ | ✅ |
| Invite to Story | ✅ | — | — |

### Step 1: Open your organization settings
Click the circle with **your initials** in the **bottom-left** corner of the Builder. This opens your **Organization settings**.

### Step 2: Invite people to your whole organization
At the top of Organization settings, open the **Team** tab. This is where everyone in your organization is listed.
Click **Invite team members** on the right. Enter the person's **email address**, choose a **role** (Admin, Editor or Viewer), and send the invitation.

|| ⚠️ Important: an organization role cascades to every project and story. If you only want someone to see one project or one story, skip this step and invite them lower down (Step 3 or Step 4) instead.

The person receives an email with a link to accept. Until they click it, they'll appear in the list with a **Pending** status.
### Step 3: Give access to a single project
Open the project you want to share, then go to **Project settings** in the left-hand menu and open the **Project members** tab.
Click **Invite member** on the right, add the **email address** and pick the **role**. This person can only reach **this project and its stories**, nothing else in the organization.

| 💡 Tip: project-level access is handy when a project is split across teams or business units and you don't want everyone seeing each other's work.

### Step 4: Give access to a single story
Open a story and click **Invite** in the **top-right** corner. You can share the story and get a review from someone else.

## Changing or removing access
Roles aren't set in stone. To **change someone's role**, find them in the member list at the relevant level (Organization, Project), open the **role dropdown** next to their name and pick a new one. The change takes effect immediately, sometimes you need to refresh your page.
Waiting on someone who hasn't accepted yet? From the member list you can **resend** a pending invitation, or **cancel** it. If they've already accepted, change their role or remove them instead.