Name the org
Owners set department options and assign members during invite or edit.
Product · Optimize & Create
Departments for each part of the team.
Assign members to departments so projects and agents default to the right lens without building separate workspaces.
Marketing stopped tripping over support's projects the week the shared workspace grew lanes.
- Department on each member
- Project and agent scoping
- Onboarding that asks once
- Works with roles
1 workspacewith per-department lanes for projects and agents, no second subscription
How it works
Scope the work
Projects and agents can follow the member department so lists stay relevant.
Onboard cleanly
New members pick a department once, then land in the right defaults.
01
One workspace, clearer lanes.
Startups share keys but not always context. Departments keep marketing, support, and ops from drowning in each other's projects.
- Member department field
- Default lens for lists
- No need for a second workspace
02
Fits the role model you already have.
Owners, admins, and members still control access. Departments add organization without inventing a new permission system.
- Works with owner and admin roles
- Feature controls still apply
- Team page remains the source of truth
Questions, answered
No. Owners, admins, and members still control access. Departments add organization, not a new permission system.
They pick a department once during onboarding, or the owner assigns it at invite. Lists then default to their lane.