Team Management

Team management operates at two levels: organisation-wide and workspace-specific.

Organisations and Workspaces

• Organisation: Company or department's main team. Required for Tellet access.
• Workspace: Project-specific team within organisation. Requires organisation membership first.

Users must be organisation members before accessing any workspace.

Organisation Member Management

Organisation Roles

Owner (one per organisation) — full control: invites and removes any member, changes any role except their own, transfers ownership, and updates organisation settings. Cannot be removed unless ownership is transferred first. Like every member, an Owner needs a workspace role to open a workspace — but Owners can always grant themselves one.

Admin — invites new members, removes members and changes roles (except the Owner), resends and cancels invitations, and manages workspaces. Cannot change or remove the Owner, transfer ownership, or modify organisation settings.

Editor — views the member list, creates workspaces, and works in assigned workspaces. Cannot invite or remove members, change roles, or otherwise manage the team.

Inviting Organisation Members

Required permissions: Owner or Admin

Steps:

1. Navigate to organisation member page
2. Click Invite to Organization
3. Enter email address
4. Select role (Admin or Editor)
5. Click Send Invitation

Invited user receives email with acceptance link and appears in member list with Pending status.

Accepting an Invitation

When the invited user clicks the link in the invitation email:

1. No existing account: they're prompted to create one (name, password, and phone number). Once they submit, the invitation is accepted and they land in the organisation with the role you assigned.
2. Existing account, no two-factor authentication: they confirm acceptance and land in the organisation immediately.
3. Existing account with two-factor authentication enabled: they're asked for their usual 6-digit code (or a backup code) before they can complete the acceptance — the same second factor as a normal login.

If the invitee has lost access to their authenticator app and has no backup codes, they cannot complete the sign-in. Cancel the pending invite and re-issue it after they've recovered access (ask them to recover access via 'Forgot password' on the login page first, then send a fresh invitation).

Managing Pending Invitations

Resend Invitation

1. Find pending member in list (orange Pending badge)
2. Click resend icon
3. Confirm resend
4. New invitation email sent

Cancel Invitation

1. Find pending member in list
2. Click cancel icon
3. Confirm cancellation
4. Invitation removed and link invalidated

Viewing Organisation Members

Member list displays:

• Profile picture or initials
• Name (or "Account Creation Pending")
• Email address
• Status badge (Green "Accepted" or Orange "Pending")
• Role (Owner, Admin, Editor)
• Date added

Changing Member Roles

Required permissions: Owner or Admin

Steps:

1. Find member in list
2. Click role dropdown
3. Select new role
4. Change takes effect immediately

Restrictions:

• Cannot change Owner's role
• Cannot change pending member's role
• Editors cannot change roles

Transferring Organisation Ownership

Required permissions: Owner only

Requirements:

• Target must be an existing Admin (promote them to Admin first if needed)

Steps:

1. Find target member in list
2. Click role dropdown
3. Click Transfer Ownership
4. Transfer completes immediately

Effect:

• Target becomes Owner
• Current Owner becomes Admin
• All permissions shift instantly

Warning: Action cannot be easily reversed. New Owner must transfer back.

Removing Organisation Members

Required permissions:

• Owner: Can remove anyone except self
• Admin: Can remove anyone except Owner

Steps:

1. Find member in list
2. Click role dropdown
3. Click Remove from organization
4. Read confirmation dialog
5. Click Confirm

Effect:

• Member loses all organisation and workspace access immediately
• Projects and other work they created remain intact

Workspace Member Management

Workspace Roles

Owner (one per workspace) — full control: invites and removes members, changes member roles, transfers ownership (the previous Owner becomes Can Edit), edits workspace settings, creates/edits/deletes projects, and deletes the workspace.

Can Edit — views workspace content, creates and edits projects, collaborates on research, invites members (as Can Edit or Can View), and removes members (except the Owner). Cannot remove the Owner, change roles, delete the workspace, or transfer ownership.

Can View — views projects, conversations, findings, reports, and analysis. Cannot create or edit projects, invite members, or modify any data.

Inviting Workspace Members

Required permissions: Owner or Can Edit

Requirement: Target must be organisation member first.

Steps:

1. Navigate to workspace
2. Click Invite button
3. Select organisation member from dropdown
4. Select workspace role (Can Edit or Can View)
5. Click Add to Workspace

Effect: Access is granted immediately, and the member is sent a notification email letting them know they've been added.

Note: Owner cannot be assigned through invitation. To give someone the Owner role, transfer ownership after adding them as Can Edit (see Transferring Workspace Ownership below).

Changing Workspace Roles

Required permissions: Owner only

Steps:

1. Open workspace member list
2. Find member
3. Click role dropdown
4. Select new role
5. Change takes effect immediately

Restriction: The Owner's role cannot be changed directly. To hand the workspace to someone else, use Transfer Ownership.

Transferring Workspace Ownership

Required permissions: Owner only

Requirements:

• Target must be a verified workspace member with the Can Edit role

Steps:

1. Open workspace member list
2. Find target member
3. Click role dropdown
4. Click Transfer Ownership
5. Transfer completes immediately

Effect:

• Target becomes Owner
• Previous Owner becomes Can Edit

Removing Workspace Members

Required permissions: Owner or Can Edit

The Owner cannot be removed. To remove the current Owner, transfer ownership first (which makes them Can Edit).

Steps:

1. Open workspace member list
2. Find member
3. Click role dropdown
4. Click Remove user from workspace
5. Read confirmation dialog
6. Click Remove user

Effect:

• Member loses workspace access immediately
• Projects and other work in the workspace remain intact
• Workspace removed from member's list

Leaving a Workspace

To leave a workspace, ask the workspace Owner to remove you. If you are the Owner, transfer ownership to another member first (which makes you Can Edit); the new Owner can then remove you.

Permissions Reference

Organisation Permissions

• Invite members — Owner: Yes; Admin: Yes; Editor: No
• Remove members — Owner: Yes (anyone); Admin: Yes (except Owner); Editor: No
• Change roles — Owner: Yes (anyone); Admin: Yes (except Owner); Editor: No
• Transfer ownership — Owner: Yes; Admin: No; Editor: No
• Update organisation settings — Owner: Yes; Admin: No; Editor: No
• View member list — Owner: Yes; Admin: Yes; Editor: Yes
• Manage invitations — Owner: Yes; Admin: Yes; Editor: No
• Create workspaces — Owner: Yes; Admin: Yes; Editor: Yes
• Access all workspaces — Owner: No — needs a workspace role (can self-grant); Admin: No*; Editor: No*

*Must be invited to workspaces

Workspace Permissions

• Invite members — Owner: Yes; Can Edit: Yes; Can View: No
• Remove members — Owner: Yes*; Can Edit: Yes*; Can View: No
• Change roles — Owner: Yes; Can Edit: No; Can View: No
• Transfer ownership — Owner: Yes; Can Edit: No; Can View: No
• Create projects — Owner: Yes; Can Edit: Yes; Can View: No
• Edit projects — Owner: Yes; Can Edit: Yes; Can View: No
• View projects — Owner: Yes; Can Edit: Yes; Can View: Yes
• Delete workspace — Owner: Yes; Can Edit: No; Can View: No
• Edit settings — Owner: Yes; Can Edit: No; Can View: No

*The Owner cannot be removed; transfer ownership first.

Contact Support

For team management issues:

• Email: [email protected]
• Response time: We aim to respond promptly during business days
• Include: Description of issue, your role, error messages