An Organisation is the top-level container in Tellet. It represents your company or team and contains workspaces, projects, team members, and branding.
Every user has at least one Organisation (created automatically on signup), and can be a member of multiple Organisations.
Hierarchy:
An Organisation holds three things: team members (everyone who can collaborate on research), workspaces (collections of related projects with independent access control), and branding (custom themes, colours, logos, and favicons for published projects).
Organisations have three roles. The Permissions Matrix below is the quick reference; the notes here cover the rules each role enforces.
Full control: changes the Organisation name and visibility, transfers ownership, invites members (as Admin or Editor), removes members (except self), changes any member's role, manages themes, and approves or directly publishes projects (with workspace access). The Owner cannot be removed by others and cannot leave without first transferring ownership.
Manages the team and approvals: invites members (as Admin or Editor only), removes members (except the Owner), changes roles (between Admin and Editor only), manages themes, and approves or directly publishes projects (with workspace access). Cannot change the Organisation name, transfer ownership, or invite/modify the Owner role.
Works on research: creates and edits projects (with workspace access), creates workspaces, and requests approval to publish. Cannot invite or remove members, approve publications, publish directly, manage themes/branding, or access Organisation settings.
For step-by-step instructions, see the Team Management guide. The rules:
Inviting members (Owner, Admin): enter a valid email and pick a role; the invitee must accept to join. Owners can invite any role; Admins can invite only as Admin or Editor.
Removing members (Owner, Admin): the member loses access to all Organisation workspaces and projects, but their previous work stays intact. The Owner cannot be removed (transfer ownership first).
Changing roles (Owner, Admin): takes effect immediately. Owners can set any role; Admins can only switch members between Admin and Editor.
Transferring ownership (Owner only): the recipient must already be an Admin (promote them first if needed). On transfer the recipient becomes Owner and the previous Owner becomes Admin. This cannot be undone — the new Owner must transfer back.
Who can manage: Owner, Admin
Themes give published projects a professional, client-specific appearance, and you can keep multiple themes for different project types. Customisable elements: primary and secondary colours, background colours, text colours, chat interface colours, logo, and favicon.
Who can change: Owner
Personal Organisations are hidden by default; use the "Add Personal Organization" button to unhide one.
Change Organisation name — Owner: ✓; Admin: ✗; Editor: ✗
Invite members — Owner: ✓; Admin: ✓*; Editor: ✗
Remove members — Owner: ✓; Admin: ✓**; Editor: ✗
Change member roles — Owner: ✓; Admin: ✓***; Editor: ✗
Transfer ownership — Owner: ✓; Admin: ✗; Editor: ✗
Manage themes — Owner: ✓; Admin: ✓; Editor: ✗
Approve publications — Owner: ✓; Admin: ✓; Editor: ✗
Publish directly — Owner: ✓; Admin: ✓; Editor: ✗
Create workspaces — Owner: ✓; Admin: ✓; Editor: ✓
Create projects — Owner: ✓; Admin: ✓; Editor: ✓
Admin can only invite as Admin or Editor, not Owner
Admin cannot remove Owner
Admin can only change between Admin and Editor roles