Guides
Team, roles and audit log
Organizations, roles, invitations, API tokens and the history of every change.
Finding your way around#
The sidebar works top to bottom: the organization (switch it if you belong to several), search (⌘K), then the project picker with that project's pages under it. First what marketing and growth teams use every day: Experiments, Personalizations, Goals, Audiences and Locations. Then, under Setup & code, what developers work with: Feature flags, Install, Websites and Project settings. Opening a project lands on its experiments. Pick another project, or All projects, from the picker. On pages that don't belong to a project (settings, the audit log), the sidebar keeps showing the project you were last in. Below that are the organization's Team, Audit log and Settings, and Docs, which opens this documentation in a new tab.
Where settings live#
Settings in the sidebar has one menu for everything that isn't a flag or an experiment, grouped by who it affects:
| Group | Page | What's there |
|---|---|---|
| Account | Profile | Your name, sign-in email, theme (light, dark or system) and the organizations you belong to. |
| Account | Password & sessions | Change your password and see or sign out of the places you're signed in. |
| Organization | General | Organization name (admins), its ID, your role, and leaving the organization. |
| Organization | Team | Members, roles and invitations. |
| Organization | Plan & billing | The plan, its limits, upgrading, invoices and cancelling (admins change it). See Plans and billing. |
| Organization | Usage | Tested visitors this month, per project. |
| Organization | API tokens | Tokens for scripts and CI (admins). |
| Projects | Project settings | Project name, environments and SDK keys, and deleting the project. Also in the sidebar, under the project picker. |
Websites, audiences, locations and goals stay with their project in the sidebar: they are part of building experiments, not one-time setup.
Organizations#
Signing up creates an organization that you own. Everything else (projects, people, API tokens, the audit log) belongs to an organization. A person can be a member of several organizations and switch between them from the organization menu.
Roles#
| Role | Can |
|---|---|
| Viewer | Read everything in the organization: flags, experiments, results, the audit log. |
| Editor | Everything a viewer can, plus create and change projects, flags, audiences, locations, goals and experiments. |
| Admin | Everything an editor can, plus invite and remove people, change roles up to admin, manage API tokens and website blocking. |
| Owner | Everything, including granting and revoking the owner role. The last owner can't leave or be demoted. |
You can only hand out roles up to your own. When someone is demoted or leaves, the API tokens and pending invitations they created that grant more than their new role are revoked. Membership is checked on every request, so removing someone ends their access immediately.
Invitations#
Admins invite people by e-mail address and role from Settings → Team. The invitation link is valid for 7 days. New users choose a name and password and accept the Terms of Service, as at signup; existing users confirm with their password and join the organization.
The invitation is emailed to them, and the dialog also shows a link once, to send it another way. Accepting the emailed invitation confirms the address, since only someone with access to that inbox could open it. The link in the dialog is a different one: someone who joins with it confirms their address by email afterwards, as at signup.
API tokens#
Settings → API tokens creates tokens for scripts and CI. A token has a name and a role (viewer, editor or admin), so a reporting script can be read-only. The secret (sk_…) is shown once; only a hash is stored. Revoke a token to stop it immediately.
Sign-in security#
- Passwords are at least 10 characters and stored with scrypt. The sign-up form shows the requirement and a strength meter as you type, and warns when Caps Lock is on.
- Sessions last 30 days; the dashboard keeps the session in an httpOnly cookie and only its server talks to the API, so page scripts never see it.
- After 10 failed sign-ins in 15 minutes, an e-mail address is locked for 15 minutes. Unknown addresses and wrong passwords get the same answer in the same time, so the sign-in form doesn't reveal who has an account.
- Settings → Password & sessions changes your password (the current one is required) and signs you out everywhere else. The same page lists your active sessions, so you can sign out of a single one or of all the others.
- Forgot your password? on the sign-in page emails a link to choose a new one. It works once, for one hour; using it signs you out everywhere and in again. The page answers the same whether or not the address has an account, and an address gets at most 5 links an hour.
- Your sign-in email can't be changed yet.
Two-step sign-in#
Under Settings → Password & sessions → Two-step sign-in, turn on codes from an authenticator app (Google Authenticator, 1Password, Authy, Microsoft Authenticator…). Scan the QR code, enter the 6-digit code it shows, and save the 10 recovery codes: each signs you in once if you lose your phone.
- Signing in then asks for the code after the password (within 5 minutes). Codes change every 30 seconds, one step of clock drift is accepted, and a code works only once.
- Wrong codes are limited: 5 per sign-in, and 10 per person in 15 minutes, so a 6-digit code can't be guessed even by someone who has the password.
- A password reset doesn't sign you in when two-step sign-in is on: sign in with the new password and a code. Accepting an invitation with an existing account asks for the code too.
- New recovery codes (needs a current code) replace the old ones. Turning it off needs your password and a code or a recovery code. Both are in the audit log.
Email confirmation#
After signing up you get an email to confirm your address; until you do, a banner on every page offers to send it again. Password resets and notifications only go to confirmed addresses. The link in the email opens a page with a Confirm my email button, so mail scanners that open links don't use it up.
Notifications#
Under Settings → Profile → Notifications, each person chooses which emails they get (all are on at first):
| Sent when | To | |
|---|---|---|
| Guardrail alerts | An experiment makes a guardrail metric significantly worse, or is stopped for it | Editors, admins and owners |
| Scheduled starts and ends | An experiment or personalization starts or ends at its scheduled time | Editors, admins and owners |
| Usage | The organization reaches 80%, then 100%, of its tested visitors for the month (once each per month) | Admins and owners |
Product news and offers are a separate choice: off unless the person ticks the box at signup, and switched under Settings → Profile → Marketing email. Every change is recorded with its time.
Terms and consent#
Creating an account, at signup or from an invitation, needs the box for the Terms of Service and the Data Processing Agreement ticked. LiftCanary records which version each person accepted, when, and from which address and browser. When the terms change materially, everyone is asked to accept the new version the next time they open the dashboard; until then only Settings → Profile stays open, where they can also delete their account. The version accepted is shown under Settings → Profile → Legal.
Deleting your account#
Settings → Profile → Delete account deletes your account for good after you enter your password (and your two-step code, if it's on). The card says what goes with it: organizations where you're the only member are deleted too, with their projects, flags, experiments and collected events. From organizations with other members you simply leave, and the audit log keeps your earlier changes. If you're the only owner of an organization with other members, make someone else owner (or remove them) first. Records of the terms you accepted are kept, as proof, after the account is gone.
Appearance#
The dashboard has a light and a dark theme; light is the default. Pick Light, Dark or System (follows your operating system) at the bottom of the sidebar or under Settings → Profile; in the collapsed sidebar, the sun/moon button cycles through them. The choice is saved in this browser. The website and these docs have the same two themes, switched with the sun/moon button in their header.
Projects and environments#
Project settings (in the sidebar, under the project picker) renames the project and manages its environments. Editors can rename and add environments; admins can also regenerate an environment's SDK key, delete an environment (a project keeps at least one) and delete the whole project. Deleting asks you to type the key, because it can't be undone: flags, experiments, history and the events collected for it go with it, and the SDK keys stop working. Project and environment keys never change, because they appear in API paths and code.
Audit log#
Every change is recorded with who made it (a person, an API token or a system job such as system:guardrails), when, and the configuration before and after. Open it in the dashboard, or read it with GET /v1/audit-log?project=<key>.