Organisation roles
Configure it within the relevant workspace scope.
Feature
Put access boundaries where the work actually lives.
Control organisation, project, document, and portal access, then connect organisation authentication to an OIDC provider.
How it works
A clear operating path.
Configure the structure once, then use it where the work happens.
- 01
Configure
Set up organisation roles for the team’s operating model.
- 02
Use
Work day to day with project visibility in the shared workspace.
- 03
Inspect
Review oidc authentication and adjust the system as the team learns.
Capabilities
What teams can use today.
These capabilities are implemented in the current TOW product.
Project visibility
Keep it connected to project and organisation context.
Document restrictions
Use it without moving the record to a separate system.
OIDC authentication
Inspect the resulting state and history in TOW.
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 organisation roles implemented in TOW?
Yes. Organisation roles, Project visibility, Document restrictions, OIDC authentication 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