Availability. Keys reach a Dev through the four
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.
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
Experiments
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.Security
Signals
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.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.
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.