Workspaces & access
Invite the team, assign roles, and keep each workspace isolated. Owners, admins, and members see only what they are allowed to do.
Workspace-first operations
Work Pilot is built for teams that plan work, execute it daily, and need the operational controls that come with real tenancy: roles, audit, SSO, and a command center.
Today in operations
Due today
Product Launch
Client Onboarding
Job queue
The same workspace covers delivery work and the operational layer around it—not a separate admin product bolted on later.
Invite the team, assign roles, and keep each workspace isolated. Owners, admins, and members see only what they are allowed to do.
Create projects, move tasks across statuses, and keep subtasks, labels, attachments, and owners on the work itself.
Start from My work, overdue, and unassigned views. The board, list, and activity feed stay in the same workspace.
Comment on tasks, mention teammates, and get notified in-app or by email. Search and the command palette jump you to the record.
Run automation rules, acknowledge incidents, follow playbooks, and watch job-queue health without leaving the workspace.
Configure SSO, review audit events, manage policies and backups, and handle workspace billing from one admin surface.
Start with a workspace, put work on projects, run the day from inbox and board, then operate with the same access model.
01
Create a workspace
Create a workspace inside your organization, invite members, and choose roles before any project work starts.
02
Plan the work
Add projects, statuses, and owners so the board and inbox have a real source of truth.
03
Run the day
Move tasks, comment, attach files, and clear overdue work from the inbox and board.
04
Operate the workspace
Use automation, incidents, analytics, and admin controls as the team grows.
Work Pilot assumes more than one team will share the product. Access, identity, and audit are part of the workspace, not a later add-on.
Capabilities are checked per workspace. Guests and members do not get admin actions by default.
Continue with SSO using a workspace slug when identity is managed by your IdP.
Sensitive admin actions are auditable, and workspace data stays behind membership and RLS.
Create an account, set up your first workspace, and run projects with the same access model you will use in production.