/Docs
Start free

Team and permissions

A workspace is shared by its members. Invite them by email, give each a role, group them into teams for routing, and decide which actions only the owner may take.

Invite teammates

  1. 1
    Settings, then Members, then Invite members.
  2. 2
    Enter one or more email addresses, pick a role for them and, optionally, a team they should join on arrival.
  3. 3
    Each address gets an email with a link. The link is good for seven days; Pending invitations on the same page lets you resend or revoke one.
  4. 4
    The invitee signs in with the code sent to their email (there are no passwords) and lands in the workspace. Sign-in with Google works too, and Sellio matches it to the invited address.
ℹ
A pending invitation holds a seat against the plan limit until it is accepted or revoked; see Plans and billing.

Roles

Owner
One per workspace, the person who created it. Can do everything, including delete the workspace, set the policies below, and transfer ownership to another member.
Admin
Manages the workspace: members, billing, channels, settings, AI agents, automations. Cannot delete the workspace or change the owner's policies.
Member
Works the inbox: conversations, contacts, tickets, their own availability and notifications. Sees settings the owner has not restricted; sees billing but cannot change it.

Change a role from the member’s row: Make admin, Make member, Remove from workspace. Transfer ownership is on the owner’s own menu and asks for confirmation; the former owner becomes an admin.

Teams

A team is a named group of members, with an icon, for routing and ownership: Billing, Technical, Sales. A conversation or a ticket can be assigned to a team as well as to a person, an automation can route to one (the Triage issues to teams template does), and the inbox has a view per team. Teams are created under Settings, then Members, and are available from the Essentials plan.

Owner policies

Under Settings, then Members, the owner can restrict what admins and members may do. Each is enforced in the API, not only hidden in the interface.

Prevent delete
Deleting conversations, contacts, tickets and messages becomes owner-only.
Prevent export
The contacts CSV export becomes owner-only.
Restrict settings
Workspace and chat settings become owner-only; the pages leave the navigation for everyone else.
Restrict AI
The AI agent area, its knowledge sources and its playground become owner-only.
Collect logs
Off stops the audit log recording changes for this workspace.

Sign-in and security

  • Sign-in is passwordless: a six-digit code by email, valid for ten minutes, three attempts. There is no password to reset or leak.
  • Notify on login, under the same Permissions block, emails the owner whenever anyone else signs in.
  • The desktop apps sign in through the browser and hand the session back to the app; see Desktop app.
  • API keys and the widget identity secret are workspace-level; both are under Settings, then Install.

Updated . Something wrong or missing? Tell us.