Skip to main content

Welcome to TOW

TOW, The Only Workspace, keeps company context, daily operating rhythm, docs, tasks, decisions, risks, projects, and AI-assisted work in one private workspace. The product is built around a simple operating rule: important facts should become durable, reviewable workspace context instead of disappearing into chat history.

Use this guide when you are setting up a new workspace, joining an existing organisation, administering a project, or operating TOW day to day.

Who this manual is for

AudienceUse these docs for
Normal usersToday, Chat, Docs, Memory, Tickets, Inbox, and personal settings.
Project adminsProject access, Check-In settings, workflows, custom fields, boards, roadmap, and ticket conflict review.
Organisation adminsMembers, invites, groups, profile locks, organisation settings, and project visibility strategy.
Server adminsRuntime configuration, deployment, secrets status, uploads, backups, AI providers, and data controls.
Review before trusting generated work

TOW can propose memory changes, tickets, roadmap changes, and snapshot text. Treat those proposals as drafts until a person reviews and accepts them.

Start with the basics

Start with TOW concepts if you are new to the product. Then use First workspace setup and Onboarding and first snapshot to create the initial trusted baseline.

If a page looks empty or unexpectedly narrow, read Navigation, project scope, and AI status. Project scope is one of the most common reasons users think data is missing when it is only filtered.

When you need steps

Use How-to guides when you already know the task and need the click-by-click workflow. Start there for tickets, boards, custom fields, workflows, board card design, ticket visual indicators, Docs, Chat, AI proposal review, standups, and teammate onboarding.

Daily work

Use the command center pages when you are operating the workspace:

  • Today for focus, project Check-Ins, proposals, drift, and roadmap review.
  • Inbox for review queues.
  • Chat for grounded questions, references, attachments, and pending actions.
  • Agent Run status when a generated result is queued or still processing.

Knowledge and execution

Use Memory, Memory diffs, Docs wiki, Snapshots, and Search and references to keep TOW grounded in context that people can inspect.

Use Tickets, Roadmap and epics, Decisions, risks, and experiments, and TQL query language to manage execution.

Administration

Project and organisation administrators should read Projects and scope, Project access roles and groups, Workflows, Custom fields, and Project boards before changing live project settings.

Server administrators should read Install TOW, Server settings, Runtime configuration, and Security and AI data controls before deploying TOW for a team.

When something does not behave as expected

Use Permissions, Statuses and lifecycles, and Troubleshooting for quick answers about access, state changes, blocked workflow transitions, hidden board cards, uploads, and Agent Run delays.

Prefer archive when you are unsure

Many TOW areas support both archive and delete. Archive keeps history available for review. Delete is for cases where the record truly should be removed.