Workspace
Organization-level container. Billing, connectors, and team management.
Project
Initiative-level space. Tasks, files, services, and members.
Task
A single unit of work. Solve or Build with its own chat and outputs.
Access cascades downward.
- A workspace member can access all projects in the workspace based on their role.
- A project member can access all tasks in the project.
- Task-level sharing does not grant access to the parent project or workspace.
When to use which level
| Level | Best for | Example |
|---|---|---|
| Workspace | Core team members who need access to everything: billing, connectors, all projects | Co-founders, full-time team members, department leads |
| Project | Collaborators working on a specific initiative | A freelancer helping with a product launch, a cross-functional squad |
| Task | External reviewers or stakeholders who only need to see one output | Sharing a Solve report with a client, sending a Build preview for feedback |
- Share a task first.
- If the person needs more context, invite them to the project.
- If they need access to everything, add them to the workspace.
Roles
Rocket uses three roles: Owner, Editor, and Viewer. These roles apply across all levels. Roles set at a higher level cascade down but can be made more restrictive at lower levels.| Role | Can do |
|---|---|
| Owner | Full control: create, edit, delete, invite members, manage billing and settings |
| Editor | Day-to-day work: create tasks, edit, upload files, connect services, comment |
| Viewer | Read-only with commenting: see all outputs and leave feedback, but cannot create or edit |
What’s next?
Workspace
Invite members and manage roles at the organization level.
Project
Collaborate on tasks, files, and services within a project.
Task
Share individual tasks and control visibility.