Manual › Chapter 9

👥 Collaborators

Invite team members, assign roles and permissions, manage pending invites, and understand the collaboration hierarchy.

Overview

SysHub has a multi-level collaboration system that lets you share access to your projects and products with team members. You control exactly who can see what, and what they are allowed to do, through a combination of scopes, roles, and permissions.

ℹ️
Only the owner of a project can invite and manage collaborators. Collaborators cannot invite other collaborators.

Collaboration Hierarchy

Collaboration in SysHub is organised in four nested scopes:

Scope What it grants access to
🏠 Account All projects and products owned by the account owner. Broadest access level.
📁 Project A single project and all its products. Collaborators at this level can see all products in the project.
📦 Product A single product only. The collaborator cannot see other products in the project.
🔩 Part A specific part within a product. The most granular access level.

Access granted at a higher scope is automatically inherited at lower scopes. For example, a project-level collaborator can see all products in that project.

Roles

Every collaborator is assigned one of two roles:

Role Description
Viewer Can view all content (products, tasks, files, links, classes, groups, interfaces, versions) but cannot make any changes. No edit controls are shown.
Editor Can make changes according to the specific permissions granted by the owner (see below).

Editor Permissions

When inviting an editor, the owner selects which actions the editor is allowed to perform. Each permission is independent and can be toggled on or off:

Permission What it allows
Mark tasks open / done Toggle task completion status
Edit tasks Create, edit, and delete tasks; assign tasks to collaborators
Upload new versions Upload new STEP files to create new product versions
Edit info Edit product title, description, files, and links
Add classes Create new class definitions at the project level
Remove classes Delete class definitions from the project
Edit classes Modify existing class definitions (name, description, fields)
Assign classes Assign project classes to parts in the 3D viewer
Add parts to groups Create groups and add parts to them in the 3D viewer
💡
A viewer role has no permissions at all — they can only read. An editor with no permissions selected is effectively the same as a viewer.

Inviting a Collaborator

Collaborators can be invited at the account, project, or product scope from the respective Collaborators panel.

  1. Navigate to the scope where you want to grant access:
    • Project scope: Project Detail → Collaborators tab
    • Product scope: Product Detail → Collaborators tab
    • Account scope: Dashboard → Collabs tab → Account section
  2. Click the Invite button (indigo, top-right of the Collaborators panel).
  3. In the Invite collaborator modal, fill in:
    • Email address — the person must already have a SysHub account.
    • Role — choose Viewer or Editor.
    • Permissions (editors only) — check the permissions you want to grant.
    • Notify by email — checked by default; sends an email notification to the invitee.
  4. Click Send invite. A success message confirms the invite was sent.
  5. The invite appears in the Awaiting acceptance section of the Collaborators panel until the invitee accepts.
⚠️
The invitee must already have a SysHub account. If they don't have one, ask them to register at sys-hub.com first.

Pending Invites

After sending an invite, it appears in the Collaborators panel under Awaiting acceptance with an amber label. The invite remains pending until the invitee accepts or declines it.

Accepting an Invite

When you receive a collaboration invite, you can accept or decline it from two places:

From the Dashboard Collabs tab

  1. Go to the Dashboard and click the Collabs tab. The tab badge shows the number of pending invites.
  2. Find the invite in the Pending invites received section.
  3. Click Accept to join the collaboration, or Decline to reject it.

From Notifications

  1. Click the bell icon in the header to open the Notifications panel.
  2. Click the invite notification. You will be navigated to the relevant project or product.
  3. Accept or decline from the Collabs tab.

Managing Collaborators

Once a collaborator has accepted an invite, they appear in the active collaborators list. As the owner, you can update or remove them at any time.

Changing a collaborator's role or permissions

  1. Open the Collaborators panel for the relevant scope.
  2. Find the collaborator row and click Edit (pencil icon).
  3. Change the role or toggle individual permissions.
  4. Click Save. Changes take effect immediately.

Removing a collaborator

  1. Find the collaborator row in the Collaborators panel.
  2. Click Remove (trash icon). Confirm the removal.
  3. The collaborator immediately loses access to the scope.
ℹ️
Removing a collaborator at the project scope does not automatically remove them from product-level collaborations within that project. You must remove them from each scope separately if needed.

Inherited Collaborators

When viewing the Collaborators panel on a product, you may see a section labelled Inherited from project. These are collaborators who have access via the project scope — they are shown read-only and cannot be managed from the product panel.

To change an inherited collaborator's access, go to the Project Detail → Collaborators tab and manage them there.

Leaving a Collaboration

If you are a collaborator (not the owner) and want to remove yourself from a project or product:

  1. Go to the Dashboard → Collabs tab.
  2. Find the project or product you want to leave.
  3. Click Leave on the collaboration card.
  4. Confirm. You immediately lose access to that scope.

Notifications for Collaborators

SysHub sends notifications to keep collaborators informed:

Event Who is notified
Collaboration invite sent The invitee (email + in-app notification)
Task assigned to a collaborator The assignee (in-app notification)
Invite accepted The owner (in-app notification)

All notifications appear in the bell icon panel in the header. Unread notifications show a red badge count. Click a notification to navigate to the relevant page and mark it as read.

Part-Level Collaboration

For very granular access control, SysHub supports collaboration at the part level — granting a person access to a specific part within a product.

🔒
Part-level collaboration is the most restrictive scope. Use it when you need to share a specific component with an external supplier or specialist without exposing the full assembly.
← Previous3D Viewer