Skip to content
Roles & teams

Give everyone exactly the right access

Decide who can configure the AI engine, who can spend credits and who is allowed to approve what it produces. Permissions are multi-role and scoped to organisations, projects and teams.

Start freeAll features
    Storefront · Members
    TT
    Tomás T.
    tomas@acme.co
    EditorApprover
    CD
    Camille D.
    camille@acme.co
    Editor
    LM
    Lars M.
    lars@acme.co
    ApproverViewer
    DT
    Design team
    4 members
    Team
    Why it matters

    Access that scales with your org

    As more people touch your content, loose permissions become a liability. TextSetu keeps access tight and easy to reason about.

    One person connected to two full-strength role badges at once, and a third behind them. Users can hold several roles at once, like editor and approver, without juggling duplicate accounts.

    Multi-role by design

    Hold several roles at once, on one account.

    Three nested scopes, with the grant landing on the innermost one. Grant access at the level that fits, from the whole organisation down to a single project or team.

    Org, project & team scope

    Grant at the level that fits: organisation, project or team.

    An invitation going out and a seat coming back filled, roles already attached. Send an invitation and new collaborators join with the right roles the moment they accept.

    Invite and go

    Invite someone and they arrive with the right roles.

    Roles for every collaborator

    One permission model, three levels

    Org-wide roles, per-project roles, and teams you can assign in one move.

    Assign organisation-wide roles for admins, per-project roles for the people doing the work, and group collaborators into teams you can assign in one move. Everyone sees exactly what they should.

    • Organisation roles owner, admin, editor and viewer for org-wide control.
    • Project roles admin, editor, viewer and approver, set per project.
    • Teams group people once and assign the whole team to a project.
    Storefront · Members
    TT
    Tomás T.
    tomas@acme.co
    EditorApprover
    CD
    Camille D.
    camille@acme.co
    Editor
    LM
    Lars M.
    lars@acme.co
    ApproverViewer
    DT
    Design team
    4 members
    Team
    Onboarding without the busywork

    Invites, cascades and a clean audit trail

    Invite by email; organisation, project and team roles activate together when they accept.

    Invite new or existing users by email. When they accept, their organisation, project and team roles activate together. Change or remove access anytime, and every change is recorded.

    • Email invitations new and existing users accept before they get access.
    • Cascade activation one accept activates org, project and team roles at once.
    • Change anytime update or remove roles, with every change on the record.
    See progress analytics
    The activity log naming who took each action: the person, whether it was a user or the system, what they did, which entity it affected and when.
    Works with the rest of TextSetu

    Explore related features

    Approval workflows

    Give reviewers the approver role and control who signs off on AI output.

    See how approvals work

    Glossary & QA

    Glossaries are access-controlled to the right people, too.

    See how the glossary works

    Progress analytics

    The activity log records who did what, human or machine.

    See what analytics show you

    Bring your whole team on board

    Invite translators, reviewers and developers with the right access in seconds. Free during early access.

    Start freeRead the docs