Team and roles

Workspace → Team. Everyone signs in by magic link; there are no passwords to issue, reset or leak.

Roles

Role	Can
Conversation viewer	Read conversations. Nothing else.
Viewer	Read everything: conversations, leads, gaps, analytics.
Analyst	Everything a viewer can, plus the day-to-day work — handling leads and conversations. Cannot change configuration.
Admin	Configure agents, integrations, actions, notifications and team.
Super admin	Everything in the workspace, including deleting it.

The line that matters is between analyst and admin. Analysts read everything and do the daily work; they cannot change what the assistant says, where it posts data, or who else gets in. That is the right default for support and sales staff.

The person who creates a workspace is its super admin.

Note

There is also a platform-admin flag, held by the operator of the installation rather than by a workspace. It is not something a workspace can grant itself.

Adding people

Add an email address and pick a role. They get a magic link on their first sign-in attempt. Removing someone takes effect immediately — their next link will not work, and any live session stops being honoured.

Claiming an email domain

Rather than adding colleagues one at a time, a workspace can claim its email domain. Anyone with a mailbox on it can then sign themselves in as a conversation viewer, without an invitation.

To prove the domain is yours, create a TXT record:

_leadai-verify.example.com   TXT   "<token from the dashboard>"

Public email providers cannot be claimed — nobody gets to own gmail.com.

The record is the switch

A DNS-verified domain is re-checked on every self-service sign-in, not just once at setup. Removing the TXT record immediately stops new people joining through it. That makes the record your off switch — keep it, and keep it somewhere your DNS cleanups will not find it.

A platform admin can also vouch for a domain instead of DNS, for cases where the customer cannot edit their own DNS.

What a workspace cannot see

Agents belong to a workspace, and everything is scoped to it: conversations, leads, gaps, analytics, actions, API keys and MCP tools. A member of one workspace has no path to another’s data, including through the API, the assistant or the MCP server.