Organizations

An organization is a Solari workspace. Sessions, profiles, API keys, browsers, billing, and usage history all live inside one. Multiple Google accounts can be members of the same organization and share everything.

Personal vs work

Every account you create on Solari starts with a personal organization — your own private workspace, not visible to anyone else. If you signed up with the Work option, you also get a separate work organization that you can invite teammates into.

The top-right org switcher in the console lets you toggle between them. Whatever org is selected scopes every page (Sessions, Profiles, API Keys, Billing, Usage) — switch before you act on data, not after.

Roles

Admin — invite and remove members, rotate API keys, change the plan, manage billing, rename or delete the organization. The person who creates an org is automatically its first admin.
Member — full read/write on sessions, profiles, replays, and API keys, but can't change billing or membership. Can leave the organization at any time.

Inviting teammates

Admins of work organizations can invite anyone with an email address. Go to Settings → Members → Invite a teammate, enter the email, pick Member or Admin, click Send. You'll get a copyable invite link to share with them directly.

We don't send invite emails yet — copy the link from the green banner after sending the invite and share it via your team's preferred channel. Invite links expire after 14 days and are single-use.

The invitee signs in (or signs up) with the invited email, opens the link, and clicks Join <org name>. They're instantly a member with shared access to your API keys, browsers, and saved profiles.

Centralized billing

Billing is per organization, not per user. Whoever is admin can change the plan, manage payment methods, view invoices, and redeem promo codes from the Billing page. Every member sees the current plan and remaining credit on the Billing page; only admins see the controls.

API keys are shared

API keys belong to the organization, not to the user who created them. Every member can create, list, and revoke keys from the API Keys page. The Created by column tracks which member minted each key for audit. Sessions launched with a key are billed against the key's organization regardless of which member ran the request.

Multiple organizations

You can be a member of as many organizations as you like — your personal one, a work one, and any other work orgs you've been invited to. Use the top-right org switcher to move between them. Each org has its own browsers, profiles, keys, and billing — there's no cross-org data sharing.

Need a second work organization (e.g. a sandbox separate from production)? Open the org switcher and pick + Create organization. You become the founding admin.

Leaving or removing

Members can leave an organization at any time from Settings → Members — find your row in the roster, click Leave. Admins can remove other members from the same page. The last admin can't leave without first promoting someone else.

Deleting an organization

Admins can delete a work organization from Settings → Organization → Danger zone. You'll be asked to type the organization name to confirm. The delete cascades to every session, profile, API key, and usage record — it can't be undone.

If the organization has an active Stripe subscription, the delete dialog will offer to cancel the subscription as part of the delete. Otherwise, cancel the subscription on the Billing page first.