Members and roles
Plans: Starter (1 seat) · Growth (5 seats) · Pro (20 seats) · Agency (unlimited)
Each Clione org has one or more members. This page covers how to invite, manage roles, transfer ownership, and understand the role permission model.
Sidebar → Org → Members tab.
Roles
Clione has four roles, in order of authority:
| Role | What they can do |
|---|---|
| Owner | Everything an admin can do, plus: change billing, transfer ownership, delete the org. One owner per org. |
| Admin | Manage stores (add, edit credentials, delete). Manage members. Manage org branding. Run enrichments, sync, propagation. View billing (read-only). |
| Member | Run enrichments, sync, edit FAQs, run verification on stores they're invited to. Cannot manage members, billing, or org-wide settings. |
| Ghost | Internal: a placeholder role given to invited users who haven't accepted yet. Becomes a real role when they accept the invite. |
Superadmin is a system-wide role used only by the Clione team for support — it's invisible from your members list.
Inviting a member
Available to owners and admins.
- Org → Members → + Add member.
- Enter the email.
- Pick a role: Admin or Member.
- Click Add.
What happens:
- An email is sent to the address with a sign-up / sign-in link.
- If the email isn't yet a Clione user, they create an account; if it is, they accept the invite.
- The row appears in the Members table immediately with the Ghost role, switching to the chosen role on accept.
If you hit your plan's seat limit, the add modal blocks the click with a clear error. Buy an extra-seat add-on from Billing, or upgrade the plan.
Changing a role
Available to owners only (admins can't promote other admins).
- Find the row.
- Open the row menu (
⋮) → Change role. - Pick the new role.
Changes apply immediately. The affected member is notified via email.
Removing a member
Available to owners and admins.
- Row menu → Remove.
- Confirm.
The member loses dashboard access immediately. Their work history (enrichments, FAQ edits, etc.) remains attributed to their email for the audit log.
Transferring ownership
Owners only.
- Find the target row (must be a current admin or member).
- Row menu → Transfer ownership.
- Type the target's email to confirm.
After transfer:
- The target becomes Owner.
- You become Admin.
- An email goes to both of you confirming the change.
There can only be one Owner per org.
Seat usage
The Members tab shows a Seats counter at the top: "Using X of Y seats". This counts only active members (Ghost invites count too — they're holding a seat).
If you're over your seat limit (e.g. after a downgrade), the counter goes red and you can't add more members until either:
- You remove someone, OR
- You buy an extra-seat add-on, OR
- You upgrade the plan.
Multi-tenant access (Agency)
If you're a member of multiple orgs (common for Agency plan team members or for cross-org consultants), you can switch between them via the Tenant Selector in the top-left header. Each org has its own roles, stores, and billing.
When you switch tenants, the entire dashboard re-scopes — sidebar, store list, current usage, billing. There's a brief loading state during the switch (~1 second).
Members are per-org. Removing someone from one org does not affect their membership in others.
Detailed permission matrix
| Action | Owner | Admin | Member | Ghost |
|---|---|---|---|---|
| View dashboard | ✓ | ✓ | ✓ | — |
| View store list | ✓ | ✓ | ✓ | — |
| Add store (BigCommerce or Shopify) | ✓ | ✓ | — | — |
| Edit store credentials | ✓ | ✓ | — | — |
| Delete store | ✓ | ✓ | — | — |
| Run sync | ✓ | ✓ | ✓ | — |
| Run enrichment (single + bulk) | ✓ | ✓ | ✓ | — |
| Edit FAQs | ✓ | ✓ | ✓ | — |
| Edit branding (org-level) | ✓ | ✓ | — | — |
| Toggle per-store badge | ✓ | ✓ | — | — |
| View billing | ✓ | ✓ (read) | — | — |
| Change plan | ✓ | — | — | — |
| Buy add-ons | ✓ | — | — | — |
| Add members | ✓ | ✓ | — | — |
| Change roles | ✓ | — | — | — |
| Remove members | ✓ | ✓ | — | — |
| Transfer ownership | ✓ | — | — | — |
| Delete org | ✓ | — | — | — |
| Generate API keys | ✓ | ✓ | — | — |
| View audit log | ✓ | ✓ | — | — |
| Install Schema Injector | ✓ | ✓ | — | — |
| Install FAQ widget | ✓ | ✓ | — | — |
| Run Pulse scans | ✓ | ✓ | ✓ | — |
The same matrix applies regardless of whether the org has BigCommerce stores, Shopify stores, or both.
Per-platform notes
Roles are platform-agnostic. A member's role applies across all the org's stores regardless of platform. There is no per-store role today — that's a planned feature for Agency tenants who want to restrict a freelancer to one specific store.
BigCommerce store role mapping
When you're an admin who needs to add or edit a BigCommerce store, you'll need a BC user with the Store admin role on the BC side to mint the API token. The Clione admin role does not grant BC-side permissions automatically — it just lets you paste the BC token Clione will use.
Shopify store role mapping
Same model. Adding or editing a Shopify store from Clione requires a Shopify user with Develop apps permission to create the Custom App and copy the Admin API access token. Clione's admin role only lets you paste the resulting token.
Agency sub-tenant access
Agency-plan tenants can manage multiple sub-tenants (one per end-client). Each sub-tenant has its own member roster — a freelancer assigned to "Client A" can't see "Client B". The Agency owner is implicitly a member of every sub-tenant with full admin rights and can switch between them via the Tenant Selector.
To grant a freelancer access only to one sub-tenant, invite them to that sub-tenant directly. Do not invite them at the Agency level — that would give them visibility into all sub-tenants.
Superadmin (internal team only)
Clione's own support team uses an internal Superadmin role to assist customers. From a customer's perspective:
- Superadmins are not counted as members of your org.
- They do not appear in your Members table.
- They can be granted temporary impersonation access to debug an issue, which appears in your audit log as
impersonation_started/impersonation_endedentries with the support user's name. - Impersonation is always logged — there is no silent access.
If you have concerns about an impersonation entry, contact support@clione.ai and request the case ID.
Email notifications
Members receive emails on:
- Invitation (to the invited email).
- Role change (to the affected member).
- Removal (to the removed member).
- Password reset request (to the user's own email).
- Suspicious sign-in (new device, new IP / country).
Org admins additionally get notified on:
- New invitation accepted.
- Seat limit reached.
- Plan downgrade pending and would exceed limits.
You can mute non-security notifications under Account → Notifications.
Troubleshooting
Invited member didn't get the email — Check spam. Resend by removing the Ghost row and re-adding the email. If still nothing, the email may be blocked by their corporate filter — give them the dashboard URL and ask them to sign up with the same email directly; the pending invite auto-resolves on sign-up.
Can't change a role despite being an admin — Only owners can change roles. Ask the owner.
Members tab shows "Tenant required" briefly during tenant switch — Known bug (#96). The page re-mounts during impersonation switching and briefly has no tenant context. Wait a few seconds and the table loads. If it persists past 30s, hard refresh.
Transfer ownership button is greyed out — You can only transfer to a current admin or member. If the target isn't a member yet, add them first, then transfer.
Seat counter shows the wrong number after removing someone — Cache. Hard refresh. If it persists, ping support — we've patched this once (#94) but it can resurface around impersonation edge cases.