Management & Security/Compliance
This section is for administrators, SREs, and anyone responsible for keeping an ABetterChoice workspace healthy and auditable. It answers:
- Who can do what inside a project?
- What changed, when, and by whom?
- Where does our data live and what compliance posture do we have?
Quick Links
| Topic | Use it when… |
|---|---|
| Workspace Overview | You need to understand projects, owners, and the surface area an admin manages. |
| User Roles and Permissions | You want to invite teammates or change who can edit experiments and configs. |
| Change Management | You need to audit who changed an experiment or remote config and when. |
| Security & Compliance | You need to answer a security review or check data-residency commitments. |
Core Concepts
- Project — the top-level isolation boundary. Experiments, configurations, metrics, audiences and members are all scoped to a single project. The current project ID is shown in the URL (
/app/<project_id>/...) and in the workspace switcher at the top-left of the console. - Role — controls what a member can read or modify inside a project. ABetterChoice ships with two roles:
adminandmember. See User Roles and Permissions. - API Key — credential used by Server SDKs, Client SDKs and the HTTP API to fetch assignments, read configurations, and report exposures. Keys are managed under Settings → SDK&Key.
- Change History — every experiment and remote configuration keeps a per-object timeline. See Change Management.