Member roles
Manage organisation membership and assigned roles.
Feature
Put access boundaries where the work actually lives.
Control organisation, project, document, and portal access, then choose the organisation authentication method that fits your identity environment.
How it works
A clear operating path.
Configure the structure once, then use it where the work happens.
- 01
Edit member roles
Assign organisation roles, groups, titles, and profile details.
- 02
Apply project access
Set explicit member permissions for the project.
- 03
Map identity claims
Map OIDC attributes to organisation identity fields.
Capabilities
What teams can use today.
These capabilities are implemented in the current TOW product.
Project access
Apply explicit member permissions.
Document access
Restrict a document to named members and teams.
Authentication methods
Start with Microsoft Entra ID, Okta, Google Workspace, Active Directory, or generic SAML and OIDC.
Control point
AI follows the same boundary.
Where AI is enabled, accessible context and review-oriented flows apply to the surrounding workspace rather than bypassing its controls.
- Scoped context
- Configured provider
- Visible proposals
- Human decision
Deployment and security
Control the deployment and the boundary.
Use TOW Cloud, run TOW on controlled infrastructure, or operate an air-gapped Docker Compose deployment. Permissions, identity settings, exports, and AI provider choices stay visible to administrators.
Explore self-hosting
FAQ
Questions worth answering clearly.
Current product, deployment, and commercial boundaries.
Is member roles implemented in TOW?
Yes. Member roles, Project access, Document access, Authentication methods are part of the current product surface and are backed by the linked implementation evidence.
Can this be self-hosted?
Yes. The capability is available within the TOW application in a configured self-hosted deployment.
See TOW in your environment