> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocket.new/llms.txt
> Use this file to discover all available pages before exploring further.
# Overview
> Understand the three sharing layers in Rocket.new and how workspace membership, project access, and task sharing control who sees your work.
export const LlmsDirective = () =>
For the complete documentation index, see llms.txt.
For a lightweight markdown version of this page, append .md to the URL.
;
Rocket uses a three-level sharing model to control who can access your work. Each level sits inside the one above it, so you can grant broad access to your core team and narrow access to external reviewers without changing your project structure.
Organization-level container. Billing, connectors, and team management.
Initiative-level space. Tasks, files, services, and members.
A single unit of work. Solve or Build with its own chat and outputs.
Inviting someone at any level adds them to the workspace. Project and task invitees become workspace members and can create new threads and other work according to their role permissions. Visibility of existing work does not cascade automatically.
* A workspace member gets access to existing projects and tasks **only if** the **Grant access** checkbox is ticked when you invite them. New projects and tasks need a separate invitation.
* A project collaborator gets access to existing tasks in that project only if the **Grant access** checkbox is ticked when you invite them. New tasks are not shared automatically.
* Task level sharing grants access to the shared task and adds the person to the workspace. It does **not** automatically grant access to other projects or tasks in that workspace.
## When to use which level
| Level | Best for | Example |
| :------------ | :--------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------- |
| **Workspace** | Core team members who need organization-level access: billing, connectors, and shared 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 |
Start narrow and expand as needed. Share a task first. If the person needs more context, invite them to the project. If they need visibility across existing projects, invite them at the workspace level with the grant access option.
Even a task or project invite adds the person to the workspace, so they can create new work according to their role. Reserve workspace level invitations with grant access for people who need broad visibility of existing projects.
## Roles
Rocket uses two roles: **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 |
| :--------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Editor** | Day to day work: create tasks, edit, upload files, and connect services. Invite at the workspace level when the invite toggle is enabled. At the project or task level, only the owner can invite. |
| **Viewer** | Read-only: see outputs, but cannot create or edit |
See [workspace roles and permissions](/getting-started/collaboration/workspace#roles-and-permissions) for the full permissions breakdown.
## Credit limits
Every member you add, whether at the workspace, project, or task level, is a member of the workspace that contains that work. Credit limits apply only to **Editors**. After an Editor accepts the invitation, they are assigned a default of **100 credits** for all time. Until they accept, the credit limit shows as **0**. You can change this at any time from **Settings → Members** using the **Credit limit** dropdown on the member's row. Owners and Viewers are not assigned a credit limit.
The credit limit controls how many credits that Editor can consume across all their activity in the workspace. It is a one-time allotment, not a monthly reset. Setting a limit to **0** prevents them from generating any output. You can update or remove the limit at any time.
All collaboration invitations are delivered via email. You can track join events, incoming share requests, and responses from the **Requests** tab in the [notification panel](/getting-started/account/notifications).
## What's next?
Invite members and manage roles at the organization level.
Collaborate on tasks, files, and services within a project.
Share individual Solve or Build tasks by email.