Add members to a Rocket.new workspace, assign editor or viewer roles, and manage access for everyone working across all projects inside.
The workspace is the top level of Rocket’s three-level sharing model. Use this level for core team members who need broad access across your organization.
Workspace access is not dynamic. When you invite someone, they get access to existing projects and tasks only if the Grant access checkbox is ticked. Any project or task created after the invitation is not automatically shared and requires a separate invitation at the project or task level.
Click your workspace name in the top-left of the sidebar.
Click your workspace name to open the menu
2
Click Invite members
In the dropdown, click Invite members. You can also reach this screen via Settings → Members.
Select Invite members from the workspace dropdown
3
Enter email and choose a role
Type one or more email addresses and choose a role for the invitee: Editor or Viewer. See Roles and permissions for details.
Enter an email address and select a role
4
Choose project access scope
Before sending, decide how much of the workspace to share. The Grant access to all projects and tasks checkbox is available for both Editor and Viewer invites:
Checkbox ticked: the invitee gets access to all projects and tasks that currently exist in the workspace. Projects or tasks created after the invitation are not included and must be shared separately.
Checkbox unticked: the invitee joins the workspace with an empty view. They can create new projects and tasks but cannot see any existing ones. Existing and future projects must be shared with them at the project or task level.
Grant access checkbox (available for both Editor and Viewer invites)
Click Invite when ready.
5
Set a credit limit
After sending the invitation, the invitee appears in the members list with a Pending badge. Credit limits apply only to Editors. Until the invitation is accepted, the credit limit shows as 0. After the Editor accepts, they are assigned a default of 100 credits for all time. Use the Credit limit dropdown on their row if you want to change this value. Owners and Viewers are not assigned a credit limit.
The invited Editor appears as Pending with a credit limit of 0 until they accept
Credit limits apply only to Editors, at all collaboration levels: workspace, project, and task. The allotment is for all time (not monthly). You can set or update the limit at any time from Settings → Members.
6
Change the credit limit (optional)
If the default of 100 credits does not fit your needs, open the Credit limit dropdown on the Editor’s row and choose a different value. Available options range from 0 to 10,000. Setting the limit to 0 prevents the Editor from generating any output.
Select a different credit cap from the dropdown
7
Invitation sent
The member appears in the list as Pending until they accept. Once accepted, their status updates and they can access the workspace according to the role and scope you configured.
The member is listed as Pending until they accept the invitation
The invitee receives an email with a link to join. You can also copy the invite link directly using the copy icon next to their name in the members list. Invitation requests can also be accepted or rejected through notifications, in addition to email and the invitation link. When they accept or reject, you will see a confirmation in the Requests tab of the notification panel.
The Requests tab confirms when an invitation is accepted or rejected
Rocket uses two roles across all levels. The table below shows what each role can do at the workspace level.
Permission
Editor
Viewer
View tasks and outputs
Yes
Yes
Create new tasks
Yes
No
Edit tasks (chat, iterate)
Yes
No
Upload and manage files
Yes
No
Connect and disconnect services
Yes
No
Invite members
Yes, at the workspace level only when the invite toggle is enabled. At the project or task level, only the owner can invite. Editors who do not own the work can never invite.
No
Change member roles
No
No
Delete projects
Yes
No
Manage billing
No
No
Editor
Day to day collaborator. Editors can create tasks, iterate on existing work, upload files, and connect services. When the invite toggle is enabled, they can invite new members at the workspace level. Editors who do not own a project or task can never invite anyone to it. Only the project or task owner can invite collaborators. When the toggle is on, the owner can invite anyone. When the toggle is off, the owner can invite only existing workspace members.
Viewer
Read-only access. Viewers can see tasks and outputs they have been granted access to, but cannot create or edit anything. Ideal for stakeholders who need visibility without editing access.
Roles apply at each level independently. A workspace Editor can be given Viewer access only on a specific project.
Go to Settings → Members to change a member’s role, update an Editor’s credit limit, or remove them from the workspace.The members panel also shows credit usage for Editors, so you can see how many credits each Editor has consumed against their limit. After an Editor accepts the invitation, they receive a default of 100 credits for all time, which you can adjust at any time from this panel. Until they accept, the credit limit shows as 0. Owners and Viewers are not assigned a credit limit.
To remove someone’s access to the workspace, go to Settings → Members, find the member’s row, and click their role dropdown.
1
Open Settings → Members
Click your workspace name in the top left, select Settings, then open the Members tab.
2
Open the role dropdown on the member's row
Click the role dropdown (showing Editor or Viewer) next to the member you want to remove.
3
Click Remove
Select Remove from the dropdown. The member loses access to the workspace immediately. Their access to any projects or tasks is also removed, including individual tasks and tasks that are part of any project.
If you remove an Editor who created projects or tasks, the workspace owner automatically becomes the owner of those projects and tasks.
Invite core team members to the workspace with grant access when they need broad visibility of existing projects. Add collaborators to specific projects, and share individual tasks with external reviewers. Project and task invitees still join the workspace and can create new work according to their role; they just do not automatically see other existing projects or tasks.
