Use case
Who can see the work is a workspace decision
The problem
What gets in the way
Access is informal: a shared login, or everyone in a chat that also holds private work. You cannot invite a contractor without handing them the whole house.
What changes
After you start using it
- 01
Email invites into a specific workspace
- 02
Roles for who can invite, manage projects, or change settings
- 03
Project guests when the whole workspace is too wide
Workflow
Add the next person without widening the door
- 01
Invite a teammate as a member if they should see workspace projects they are allowed to access.
- 02
Create a role if the default member permissions are too broad or too narrow.
- 03
Invite a contractor as a guest on one project when they should not see the rest.
Projects
Projects you can access in this workspace.
Website
Operations
What you use
Capabilities in this job
- 01
Members, roles, and guests
Owners and members work in the workspace. Guests can be limited to a project. Custom roles control who can invite, manage projects, or change settings.
- 02
Workspaces, projects, and boards
A workspace is the boundary for members and projects. A project holds statuses and tasks. The board is the live kanban view: columns are statuses, cards are tasks. Opening a task uses the inspector so you stay on the board.
Questions