Multiple boards and views
Configure it within the relevant workspace scope.
Feature
Make the board reflect the process—not dictate it.
Use multiple project views and work-type workflows so the team sees a useful path through delivery.
How it works
A clear operating path.
Configure the structure once, then use it where the work happens.
- 01
Configure
Set up multiple boards and views for the team’s operating model.
- 02
Use
Work day to day with work-type workflows in the shared workspace.
- 03
Inspect
Review transition actions and adjust the system as the team learns.
Capabilities
What teams can use today.
These capabilities are implemented in the current TOW product.
Work-type workflows
Keep it connected to project and organisation context.
Status transitions
Use it without moving the record to a separate system.
Transition actions
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 multiple boards and views implemented in TOW?
Yes. Multiple boards and views, Work-type workflows, Status transitions, Transition actions 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