Clear roles, every action logged.
Share Probant with your team and your agency: permissions set action by action, launches reviewed by another member, a log of every change, and two-factor authentication when the workspace requires it.
- Camille Rouxsince Nov 24, 2025Owner
- Hugo Bernardsince Nov 26, 2025Editor
- Inès Martinsince Jan 12Editor
- Léo Garniersince Feb 2Agency
- lucas@example.cominvitation until Nov 13Viewer
Read the transcript
Who launched this test, and who reviewed it? Before launch, another member reviews the plan. After that, the audit log keeps every change.
Launches are requested, then reviewed. “Launch” becomes “Request approval”: the request locks the plan, then another member approves it.
If the draft changes, the approval is dropped. The request carries the draft’s fingerprint: make one more change and you have to ask again.
The audit log records who did what. Every action that changes the workspace, with its author and target, including the ones Probant takes on its own. Kept 13 months, exportable as CSV.
Everyone has a role, permission by permission. Four fixed roles, or your own, built from 25 named permissions. The owner can require two-factor authentication for everyone.
The demo is open, no sign-up needed.
Clear permissions, reviewed decisions.
The visuals come from the settings of the demo store, Maison Lune, which hands its tests to an agency; the rules are the same as in your workspace.
Four fixed roles, or your own.
Owner, editor, contributor, and viewer cover most teams. For the rest, the owner builds a role by picking from 25 named permissions: prepare tests, launch and stop tests, roll out the winning variant, approve launches, write variant JavaScript, turn feature flags on and off… In the demo, Léo Garnier works with the “Agency” role: 10 permissions of 25.
- A contributor prepares drafts, ideas, metrics, and feature flags, without launching, stopping, or rolling out
- No one can grant a role stronger than their own, to a member, in an invitation, or to an API key
- Owner only: manage billing, manage custom roles, appoint owners, and delete the workspace
| Group | Owner | Editor | Contributor | Viewer | Agency |
|---|---|---|---|---|---|
| View | yes | yes | yes | yes | yes |
| Tests and personalizations | all | all | 1 of 6 | — | 5 of 6 |
| Measurement | all | all | 1 of 4 | — | 1 of 4 |
| Feature flags | all | all | 1 of 2 | — | 1 of 2 |
| Sharing and data | all | 3 of 4 | — | — | 1 of 4 |
| Members, keys, and settings | all | 1 of 8 | — | — | 1 of 8 |
| Owners only | all | — | — | — | — |
A launch can require another member’s approval.
When the owner requires it, “Launch” becomes “Request approval”. The request locks the test plan and a fingerprint of what visitors will see. Another member approves, or rejects with a reason; if the draft changes afterward, the approval no longer applies.
- The approved test launches with the approved settings, checked on the server
- A variant’s JavaScript is shown for review in the request
- Live feature flag changes follow the same rule; the kill switch stays immediate
The audit log shows who did what, and when.
Launches, stops and decisions, rollouts, metrics, keys, members, settings: every action that changes the workspace is logged with its author, its target, and its details. Actions Probant takes on its own, such as a guardrail rollback, are signed “Probant”.
- Filters by action type, member, and period
- CSV export, in Paris time and UTC
- Kept 13 months, then deleted
Probant moved to the next step (auto-advance) the rollout of “Free shipping from €60”
Oct 8Camille Roux invited lucas@example.com
Nov 6Léo Garnier joined the workspace
Feb 2
Two-factor authentication, enforceable for the whole workspace.
Each member can protect their account with an authenticator app, with 10 single-use backup codes. The owner can require it from everyone: until a member turns it on, the workspace stays locked to them, actions included.
- The verification level is checked on the server on every request
- The owner can require it only after turning it on for themselves
Your account is protected by an authenticator app: enter the code it shows.
App codeA staging key for your staging site.
Installed on the staging site, it serves the production configuration plus drafts marked ready, as if they were running, so you can check the variant on a real page before launching it. Its events are kept apart.
- Events kept 7 days, never read by reports, segments, or guardrails
- No staging visitor counted toward the plan
In detail.
- Roles
- Owner, editor, contributor, and viewer, and up to 30 custom roles per workspace. A role still assigned can only be deleted with a replacement role.
- Permissions
- 29 named permissions, 25 of which can be assigned to a custom role; four stay with the owner.
- Invitations
- Valid for 7 days, revocable, with a role that can’t exceed the inviter’s.
- Audit log
- 191 logged actions, sorted into 11 categories; filters for 7 days, 30 days, 90 days or the full retention period; CSV export of up to 10,000 rows.
- Two-factor authentication
- Authenticator app with time-based codes, plus 10 single-use backup codes; the owner can require it for all members.
- Presence
- Online members and the page each one is on, reported every 45 seconds while the tab is visible; a member disappears after 2 minutes without a signal.
- Owner of a test
- Each test has an owner, the person who created it or the one it is assigned to; “Mine” filters running tests down to yours.
- Pinned
- Up to 8 pinned tests per person, in the menu; pinning changes nothing for other members.
- Activity feed
- Launches, decisions, rollouts, suggested ideas, guardrail stops, and alerts sent by Probant, newest first.
- Staging
- Dedicated public key; ready drafts served with, optionally, one variant shown to everyone; events kept 7 days.
- Workspaces
- One workspace per site, each with its own members, tests, and plan; up to 3 workspaces on the Free plan per owner.
- Agencies
- One view of all your workspaces, one row per client: running tests, latest verdict, quarter’s gains, decision quality.
Frequently asked questions.
Can our agency launch tests without access to billing?
Yes: give it a custom role that prepares, launches, and rolls out, without billing, members, or settings. That is the demo’s “Agency” role. Billing, roles, and deleting the workspace always stay with the owner anyway.
Who can read the audit log?
Owners, and members whose custom role includes the “View the audit log” permission. It mentions members’ addresses and keys, so it isn’t open to others.
What happens if a member hasn’t turned on two-factor authentication?
If the workspace requires it, they see the demo and a banner explaining how to turn it on for their account. The workspace stays locked to them, actions included, until they do.
Can an approved draft still change?
Yes, but the approval no longer applies as soon as what visitors would see changes: page, targeting, variants, weights, or changes. You need to cancel the request and submit it again.
Next: Visual editor
See this feature in the demo, on the screen this page describes, or move on to the next one.
- Open demo, no sign-up
- Free to start, no overage charges
- Database and compute in Amsterdam, with Scaleway