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

# Permissions catalog

> Every per site permission key, what it lets a Dev do, what it needs alongside, and which plans can pick it by hand.

Every member has a **role** (Admin, Dev or Viewer). Admins hold every key on
every site. Viewers hold none. A Dev holds, on each site, exactly the keys
granted there. This page lists them all: twenty five keys in five groups,
plus Access danger zone on its own.

> [!NOTE]
>
> **Availability.** Keys reach a Dev through the four
> [access presets](https://docs.abtestly.com/team/members-and-roles.md#access-presets) on every plan with
> a second seat, from Starter up. Picking keys one by one, a custom set, is on
> the **Pro plan and above**. Below Pro the Manage access drawer shows these
> switches locked, set to what each site has saved. See
> [pricing](https://abtestly.com/pricing).

Set keys from **Team & access → Manage access** on a Dev's row.
[Members and roles](https://docs.abtestly.com/team/members-and-roles.md) covers the drawer, the presets,
and what changes below Pro.

> [!NOTE]
>
> **Site settings in the dashboard.** A Dev opens Site settings and sees the
> tabs their keys unlock on that site. Settings only an Admin can change show
> read only. The Danger zone tab opens only for Admins: a Dev holding Access
> danger zone can use it through the API, but not from the dashboard.

## Configuration

| Key | What it lets a Dev do | Also needs |
| - | - | - |
| **Global JS** | Edit and publish the site wide JavaScript that runs before every variation | Publish experiments |
| **Code editor access** | Edit variation JavaScript and CSS in the code editor | None |
| **SPA support** | Configure route and history detection for single page apps | Publish experiments |
| **Analytics integration** | Connect and manage GA4, GTM and the other analytics adapters | Publish experiments |
| **Change time zone** | Change the site's reporting time zone | None |
| **Change currency** | Change the site's reporting currency | None |
| **Code checking** | Change the code checking level for this site | None |

## Experiments

| Key | What it lets a Dev do | Also needs |
| - | - | - |
| **Publish experiments** | Push an experiment live to traffic | None |
| **Pause experiments** | Pause a running experiment | None |
| **Schedule experiments** | Save a future start date, an end date or a maximum run length | Publish experiments |
| **Archive experiments** | Move a finished experiment to the archive | None |
| **Delete experiments** | Permanently remove an experiment. Turning it on asks for confirmation | None |

## Data

Reading and using what already exists needs no key: anyone with access to
the site can list its goals, assets, locations and audiences and attach them
to an experiment. These keys gate changing the shared definitions.

| Key | What it lets a Dev do | Also needs |
| - | - | - |
| **Add and remove assets** | Upload new files under **Assets** or delete existing ones | None |
| **Add and edit goals** | Create and edit goals in the library | None |
| **Add and edit locations** | Create and edit saved locations for targeting | None |
| **Add and edit audiences** | Create and edit saved audiences for targeting | None |
| **Add and edit campaigns** | Create, rename and archive campaigns for this site | None |
| **Exclusion groups** | Create and manage mutual exclusion groups | None |
| **Dev libraries** | Add developer libraries from outside providers to the site | None |

## Security

| Key | What it lets a Dev do | Also needs |
| - | - | - |
| **IP block list** | Add and remove blocked IP addresses and ranges | None |
| **Activity log** | See this site's entries in the activity log. A Dev who holds it on no site sees no entries at all. Admins and Viewers see the log without it | None |
| **QA session links** | Create a [QA session link](https://docs.abtestly.com/preview/qa-overlay.md) that opens every draft on this site for 24 hours | None |

## Signals

| Key | What it lets a Dev do | Also needs |
| - | - | - |
| **Access Signals** | View Signals scans, ideas and reports | None |
| **Run Signals** | Start scans and generate or build test ideas | None |
| **Manage GA4** | Connect or disconnect the Signals GA4 integration | None |

## Danger zone

Kept apart from the five groups and left out of every preset, so it is
always a deliberate grant. Turning it on asks for confirmation.

| Key | What it lets a Dev do | Also needs |
| - | - | - |
| **Access danger zone** | Delete this site with every experiment and its data, turn public preview links on or off, and revoke every outstanding preview link | None |

## The presets

The drawer has four presets, on every plan with a second seat:

* **Full access.** Every key except Access danger zone, so twenty five of
  the twenty six.
* **Standard dev.** Eleven keys for everyday build and ship work: Code
  editor access, SPA support, Analytics integration, Add and remove assets,
  Add and edit goals, Add and edit locations, Add and edit audiences, Add
  and edit campaigns, Publish experiments, Pause experiments and Schedule
  experiments.
* **View only.** Only Activity log. Reading goals and assets needs no key,
  so a Dev who should only look needs nothing more.
* **Clear all.** Every key off.

On Pro and above a preset is a starting point you can adjust switch by
switch. Below Pro the preset is the whole set: the API accepts one of the
four presets, or the set a site already holds, and refuses anything else
with `403 feature_requires_plan`.

## Companion rules

Four keys need **Publish experiments** alongside them, because each one
reaches live traffic: Global JS, SPA support, Analytics integration and
Schedule experiments.

* In the drawer, each of the four stays disabled, with "Also needs Publish
  experiments.", until Publish experiments is on.
* Turning Publish experiments off while any of them is on asks first, then
  turns them off too.
* The API refuses a set that breaks a rule. Every preset already follows
  them.

## Enforcement is on the server

The dashboard hides buttons a member does not have permission for. The API
also refuses the call, so a client that goes around the dashboard still
cannot publish an experiment without the key.

## Where the rest of this fits

* The **role** is the ceiling. A Viewer can never be given publish.
* Site scope decides which sites the keys apply to. A Dev scoped to one site
  cannot publish on another, whatever keys they hold.
* Admins have every key on every site by definition, so Manage access opens
  only on a Dev's row.


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