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.
What you use
Capabilities in this job
- 01
Projects
A workspace holds projects. A project holds statuses and tasks. The board is the live view: columns are statuses, cards are tasks. List, timeline, and calendar show those same tasks. A canvas sits on the project for the sketch that is not a task yet. Templates start the next card from work you already shaped. Opening a task uses the inspector so you stay on the view.
- 02
Chats
Public and private channels sit next to the projects. Threads and reactions stay in the channel. A project can have a linked channel so the conversation about that work has a home. Turn chats off if the team already talks somewhere else.
Questions