> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/feature-experimentation-and-rollout/user-and-access-management/folder-permissions.md).

# Folder Permissions

Within **Feature Experimentation & Rollouts (FE\&R)**, you may manage multiple folders corresponding to different products, scopes, teams, or business units.

To avoid configuration mistakes and maintain governance, you can assign **specific permissions to specific users or teams per folder**.

This ensures that each team only accesses and operates within its defined scope.

### Configuring folder permissions

To manage folder permissions:

1. Navigate to the desired **folder**
2. Open **Folder settings**
3. Access the **Permissions** section

From this panel, you can:

* Add a user or a team
* Modify their role
* Remove access
* Define their level of interaction within the folder

Changes apply immediately once saved.

{% hint style="info" %}
**Save your changes:** When modifying folder permissions, make sure to save before closing the panel.\
Unsaved changes will not be applied.
{% endhint %}

### Folder-Level roles

You can assign one of the following roles within a folder:

#### 1. Viewer

Viewers have read-only access.

They can:

* View campaigns
* Access reports

They cannot:

* Create campaigns
* Edit campaigns
* Launch or pause campaigns
* Manage folder permission

#### 2. User

Users can operate campaigns within the folder.

They can:

* Create campaigns
* Edit campaigns
* Launch and pause campaigns
* Archive campaigns

They cannot:

* Manage folder members
* Modify folder governance settings

#### 3. Admin

Admins have full operational and governance control within the folder.

They can:

* Create, edit, launch, pause, archive, and delete campaigns
* Manage folder members (add/remove users and teams)
* Modify folder-level permissions

{% hint style="info" %}
**Permission Priority**\
A user can receive permissions in two ways:

* Individually (direct assignment)
* Through a team

If a user has multiple roles within the same folder, the **highest permission level applies**.

**Example:**\
If a user is manually assigned as *Viewer* but belongs to a team assigned as *Admin*, they will have **Admin** permissions in that folder.
{% endhint %}

### Example use case

*As a member of a Product & Tech organization with multiple feature squads, I need to organize my workspace so that each team only accesses the folders within their scope.*

For example:

* Folder: Home Page
* Folder: Product Pages
* Folder: Checkout

Each squad is assigned only to its relevant folder.

Meanwhile, a Super Admin or Project Manager can still maintain global visibility and governance across all folders.

This completes the access control model:

* **Account Role** → defines global governance
* **Team** → groups FE\&R users
* **Folder Role** → defines operational permissions
* **Campaign** → execution layer


---

# 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://docs.abtasty.com/feature-experimentation-and-rollout/user-and-access-management/folder-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.