Members, teams and access
Invite members, organize teams and grant each source’s resources and tools.
Organization roles, team membership and source permissions serve different purposes. Check all three when opening access.
Invite a member
- Open Organization → Members, then Invite a user.
- Enter the email address, role and relevant teams.
- Click Create invitation.
- Copy the provided link and send it to the invitee. They can accept the invitation and sign in or create an account.
They join the chosen teams when they accept. Pending invitations occupy a seat; check the displayed capacity before creating more. You can cancel an invitation from the member list.
Reserve the Admin role for people who need to manage the organization. Use Member for people who read sources through their assistant. Owner holds organization ownership, with a dedicated transfer action.
Create and organize teams
In Organization → Teams, click New team, name it and create it. Then assign members from their profile or when inviting them.
A team lets you grant the same access to several people. A team lead can manage the scopes they lead; they do not become an admin of the entire organization.
Grant a source
In Data sources, open the source and its Access management tab.
- Review enabled tools for the source: they form the common ceiling for assigned access.
- Add recipients: teams, people or available scopes in your organization.
- Choose their resources and tools. Depending on the connector, these are tables, repositories, queries, phone lines or payroll files.
- Verify the result from a recipient’s assistant.
Aircall, SILAE and AWS in particular have tools assigned per resource. Selecting a tool globally does not replace the necessary resource permissions.
Shared sources and personal connections
Shared sources serve designated recipients within the organization. Connections in My connectors belong to the member who authorizes them; they support personal use and, depending on the provider, actions made with that account.
On a shared source, read tools are distinguished from write tools. Where a write tool is available, enabling it requires explicit confirmation and acts through the shared account. Check this effect before enabling it.
See personal connections.
Remove access
Remove the source grant or relevant team membership. Check other teams and direct grants that may still provide access to the same source.
To stop the source for all recipients, use its disable action where available, or remove the connection. Removing access does not erase data already received by an assistant.