Workspaces

Workspaces provide a collaborative environment for managing projects, verses, and archive resources within the XRHUB for groups and teams. They enable teams to organize large sets of assets, distribute work across multiple groups, collaborate in parallel, and maintain efficient and secure workflows through granular permission controls.

Default Workspace

Users with workspace permissions, or those invited to a workspace, are automatically assigned a Default Workspace.

• The Default Workspace is private by default. It is your personal workspace, created with your account, where you can work independently, invite collaborators, and manage your projects alongside other workspaces.
• It cannot be deleted, ensuring that at least one active workspace always exists.
• It can be edited to adjust settings or permissions as needed.

Types of Workspaces

XRHUB supports two types of workspaces, depending on whether you are working alone or with a team.

Private Workspaces

Workspaces are private by default. If you don’t invite other users, the workspace remains visible and accessible only to you.

Private workspaces are ideal for:

• Organizing personal projects by theme, client, or purpose
• Separating experiments, prototypes, or internal work
• Managing assets without sharing access

No other users can view or edit content in a private workspace.

Team Workspaces

A workspace becomes a team workspace when you invite other users to collaborate.

Team workspaces allow you to:

• Invite members and assign role-based permissions
• Collaborate on projects and verses within the same workspace
• Manage shared assets, version history, and access control in one place

Team workspaces are designed for structured collaboration, ensuring that users only have access to the projects and actions permitted by their role.

Scope of Workspaces

Workspaces affect only the following resources:

• Projects
• Verses
• Archive resources

All other tabs and features—such as Community, Activations, Settings, or Tiers—are global and remain accessible regardless of the selected workspace.

This means users in your workspace can access all workspace projects, verses, and archive resourses inside the XRHUB, the XR Creator Studio and the Metaverse.

Workspace Storage Ownership

Each workspace is owned by the user who created it. All projects, verses, templates, collections, and archive resources stored within a workspace use the storage quota of the workspace owner.

This means that:

• All collaborators in the workspace share the owner’s available storage
• Individual user storage limits do not apply to workspace content
• Storage usage is accumulated at the workspace level, not per member

This model ensures consistent availability of shared assets and avoids storage fragmentation across team members.

💡 Note: If you are invited to a workspace, any content you create or modify inside that workspace counts toward the workspace owner’s storage, not your personal account.

Creating and Managing Workspaces

Workspaces can be created by:

• Admins, or
• Users who have been granted Workspace permissions.

Each workspace operates independently, allowing teams to separate content, control access, and manage ownership without affecting other workspaces.

To create a workspace:

1. Locate the Workspace selector in the top navigation bar
2. Click the ➕ (Create Workspace) button
3. Enter a workspace name
4. (Optional) Invite users by entering their email addresses
   • Press Enter to add each email
   • You can add multiple emails separated by commas
   • Adjust each user’s role as needed to match the permissions you want them to have in the workspace
5. Click Create

Invited users will receive an email invitation to join the workspace. They must accept it to gain access.

Workspace permissions

Workspace permissions control what each member can see and manage within a workspace. Permissions apply to projects, verses, collections, templates, and archive resources in the selected workspace.

Each member is assigned one of the following roles:

◆ Viewer:

Users with Viewer permission have read-only access to the workspace.

Viewers can:

• View projects, verses, assets, collections, and templates
• Open and preview content

Viewers cannot:

• Edit or save changes
• Create, delete, or publish projects
• Invite or remove workspace members
• Change roles or permissions

Use this role for stakeholders, reviewers, or clients who need visibility without editing access.

◆ Contributor:

Users with Contributor permission have content editing access in the workspace.

Contributors can:

• Create, edit, and save projects
• Work with collections and templates
• Collaborate using Control Versioning (personal branches, drafts, and history)
• Publish content (if allowed by project rules)

Contributors cannot:

• Invite or remove users
• Change workspace roles or permissions
• Delete the workspace or any workspace content

Use this role for designers, builders, and collaborators actively working on content.

◆ Admin

Users with Admin permission have Ffll workspace access.

Admins can:

• Do everything Contributors can do
• Invite and remove workspace members
• Assign and change user roles
• Manage templates
• Control access and permissions

Admins cannot:

• Delete the Workspace
• Transfer the workspace

Use this role for team leads or workspace managers responsible for access control and organization.

Editing a Workspace

Workspace settings can be updated at any time:

• Rename the workspace
• Invite additional members
• Change member roles
• Remove members

Changes are saved immediately after clicking Save.

Version Control in Workspaces

Workspaces are designed to support collaboration across teams, allowing multiple users to work on the same projects without interfering with each other. To make this possible, every project within a workspace is backed by Version Control.

Version Control enables multiple contributors to work in parallel while keeping each user’s changes isolated, traceable, and safe.

Within a workspace, Version Control provides:

• Parallel collaboration without overwriting teammates’ work
• Clear visibility into active collaborators, including who is working on each branch
• Safe branch switching to review, compare, or continue work from other contributors
• Reliable, conflict-free saves, even when multiple users save simultaneously
• Controlled merging and publishing, allowing teams to combine work and deploy projects to development or production environments

This approach allows teams to iterate quickly while maintaining a complete and traceable history of changes for every project within the workspace.

To learn more about how Version Control works at the project level, see the Version Control section for Projects.