Understand organizations and workspaces
An organization owns membership, Stripe billing, subscriptions, PayGo purchases, and one pooled wallet. A workspace is the isolation boundary for lists, jobs, exports, API keys, webhooks, widgets, reports, automations, exclusions, and usage.
Every new account receives a personal organization, default workspace, owner membership, wallet, and eligible trial credits. A person can belong to multiple organizations; accepting an invitation does not transfer or combine personal credits.
Choose the least-powerful role that fits
Owners and admins have implicit access to all workspaces; contributors and viewers receive explicit workspace grants.
| Role | Can do | Cannot do |
|---|---|---|
| Owner | Billing, ownership, team, all data, developer settings, and workspace administration. | — |
| Admin | Team, all data, developer settings, reports, rules, schedules, and usage. | Stripe portal, payment methods, invoices, ownership transfer, or organization deletion. |
| Contributor | View shared data, spend credits on verification, export, and manage resources they created. | Team, billing, organization, and protected developer administration. |
| Viewer | Read permitted results and download permitted exports. | Spend credits or mutate workspace data. |
Invite teammates safely
Open Team or Clients
Owners and admins can create an invitation from the active organization.Choose the organization role
Use admin only for people who should manage every workspace. Most collaborators should be contributors or viewers.Grant workspaces
For restricted members, choose each workspace and whether access is contributor or viewer.Send and monitor
The single-use invitation expires after seven days and can be revoked before acceptance.
Invitations are limited to 20 per hour and 100 pending per organization. The invited address is encrypted, and the acceptance token is stored only as a hash.
Set up an isolated client workspace
Client workspaces are available to organizations unlocked by an active subscription or a settled PayGo purchase.
Create a client workspace
Give it a client-identifying name that does not contain unnecessary personal data.Set an optional cap
Choose a daily or monthly hard credit ceiling before importing or enabling integrations.Grant the agency team
Owners and admins already have access. Give other agency teammates explicit contributor or viewer access.Invite the client
Grant only that client workspace. The client sees members who share access—not agency billing, the default workspace, or another client.
Control a shared balance without per-seat billing
- An active subscription or any settled PayGo purchase unlocks unlimited teammates and live developer features.
- All work draws from the organization’s pooled balance; there is no Stripe quantity or per-seat charge.
- Optional daily/monthly member limits are enforced atomically with credit reservation.
- Optional daily/monthly workspace caps protect agency client budgets.
- Refunds restore the same workspace, member, user, key, and source attribution.
- Owners can see consolidated organization usage and per-workspace usage.
Handle lapses, departures, and archives
If a subscription lapses and the organization has never completed a PayGo purchase, non-owner access and live developer credentials are suspended without deleting people or data. Restoring an eligible subscription immediately restores access.
When a person leaves, creator attribution can remain while their user reference is safely removed. Shared resources do not cascade-delete with the account. Review and revoke their invitations, workspace grants, API keys, and relevant webhook/widget credentials.
Archiving a client workspace disables its keys, widgets, schedules, report links, and new verification work. Historical results and financial attribution remain available under their applicable retention rules.