Members and roles
Add people, choose their permissions, and manage account access.
5 min read
Add people under Settings > Members, then choose the role that matches their work. Roles determine permitted actions; project access, teams, and conversation assignments determine which resources a person can reach.
Add a person
You need an Owner or Admin account to manage members.
- Open Settings > Members and select Add member.
- Enter the person's Email and, optionally, Name.
- Choose a Role. Start with Member for everyday use; the comparison below explains when to grant more access.
- For a new Tale account, enter a Password that meets the displayed policy. If the email already belongs to an account, Tale reuses its credentials and hides the password field.
- Select Add member. For a new account, save the credentials shown in the confirmation before closing it, then share them through your organization's approved channel.
The person appears in the member list. Tale does not send an invitation or password-reset email for this flow: adding someone is your confirmation of their address, so the account works everywhere at once — including applications people sign in to with their Tale account. If the address is already a member of this organization, the form reports that instead of adding a duplicate.
A password set or reset by an administrator, or an expired password under the organization's rotation policy, requires the member to complete the change at sign-in. See the member-facing password-change steps.
Choose a role
| Role | Typical work | Organization administration |
|---|---|---|
| Owner | All product and administration work | Includes transferring ownership and deleting the organization, which also deletes its sandboxes and their files; deleting asks you to type the organization's name before the button enables. |
| Admin | Manage people, services, policies, and the team's work | Full organization settings; cannot transfer ownership. |
| Developer | Build agents, automations, and integrations | Technical settings such as providers, connectors, and API access; no member administration. |
| Editor | Maintain content and operate day-to-day work | Content editing; no access to Automations; connector resources are read-only. |
| Member | Use chat, read resources shared with them, and create project tasks, working their own tasks with project agents | No organization administration; can submit message feedback. |
| Disabled | No active access | Retains the membership record without granting permissions. |
Only Owners, Admins, and Developers see Automations, in the navigation and in projects; anyone else who follows a link to an automation sees Access denied.
People who are not Owners or Admins cannot open Settings > Members; they see their own role under Settings > Account > Your role.
Project tasks follow a rule of their own: every member who can open a project creates tasks in it and changes the tasks they created or that are assigned to them, while Editors and higher roles change every task. The project's settings, agents, and files stay with Editors. Manage tasks on a project board lists what a Member can do with their own tasks.
These are role capabilities, not a promise that every record is visible. Conversation reads follow assignment: a person sees work assigned to them or their teams; unassigned conversations remain with Owners and Admins for triage. See conversation routing.
Audit-log viewing is restricted to Owners and Admins. Actions by other roles can still produce audit entries; producing an entry does not grant access to the log.
Change a role or reset a password
Open the person's row menu, choose Edit, and change Role. Select Save, then check the role badge in the list. To restore a disabled member's access, explicitly select the role they should receive.
The edit dialog also changes the display name. Email is read-only. To set a replacement password, enable Update password, enter a password that meets the displayed requirements, and save. The member must choose a new password on their next sign-in; resetting the password signs the member out of all sessions. Use your organization's identity-checking process before resetting an account.
You cannot edit your own role through this menu, assign Owner through the role picker, or demote the last administrator. Existing Owners and the organization creator also have protected roles. If a change is refused, check the relevant account before trying a different role.
Transfer ownership
An Owner can choose Transfer ownership from another member's row menu. Read the confirmation carefully: the selected person becomes Owner and the transferring Owner becomes Admin. Use this action for an ownership handover, not an ordinary role promotion.
Remove or recover access
Use Disabled when access should stop while the membership remains. Use the row's Delete action to remove the membership from this organization. Removing it also deletes the separate sandbox workspaces of the agent runs the person started, with their files; Disabled keeps them. It also revokes the API keys an Owner or Admin made for the person here, and the keys the person made here for other members. Review shared work and team responsibilities first; removing membership is different from a data subject erasure request.
If a member loses an authenticator or passkey, open Edit and use the relevant security controls. Two-factor authentication explains reset, recovery, and session consequences.