Templates

Understanding Templates

Templates are workspaces that act as linked sources for other workspaces. A template provides structure, content and configuration that child workspaces use as their basis. Child workspaces stay linked to the template as long as they do not change the inherited elements.

Templates are self-contained. They do not use team files or other external data. All required content must be stored inside the template workspace.

When a child workspace is created from a template, it starts with the template’s current state. Elements are the parts of a workspace that can be inherited from a template: configuration settings, the initial and saved states, and all managed content. Elements that are changed in the child become independent. Elements that are not changed continue to follow the template when it is updated. Updates are usually applied on session start.

Template authors can define which settings can be modified in child workspaces and which settings stay fixed. This allows templates to support both flexible setups and strictly defined scenarios.

Template Behaviour

Child workspaces inherit structure, content and configuration from the template. Elements stay linked to the template until they are changed in the child workspace.

Configuration – When a configuration setting is changed in the child workspace, the configuration becomes independent. Locked settings continue to follow updates from the template.

Content – Template content such as 3D objects, images, presentations, Blox and location add-ons cannot be replaced by child workspaces. Child workspaces may add their own content and can control visibility of template content in their sessions and save states.

Save State – When continuous saving is enabled in a child workspace or an Initial State is created through Edit Mode, the child workspace restores from its latest saved state. Changes made to the template no longer appear in the child workspace.
Title and Visuals – Child workspaces inherit title, tile and poster by default and can be changed individually.

Members – Members are not inherited, each child workspace manages its own members. Templates allow access to Owners and Admins only.
Setting Locks – Template creators can lock specific parameters. Locked settings cannot be changed in child workspaces.

Deletion – A template cannot be deleted while child workspaces exist.

Create a Template

 
Create — Templates are created from the Workspaces section in your Team. Select an empty slot, choose Template as the workspace type, and assign an owner. Templates appear in the workspace list of the assigned owner. Templates are a variant of workspaces and follow the same creation process as regular Workspaces.

Publish — Publishing makes the template available to your team. Your published templates appear in the configuration section of an empty workspace. Ensure the template is fully tested before publishing.

Modify — Templates can be edited at any time. Changes affect all child workspaces unless a child has already modified the corresponding elements.
Public Distribution — Templates can be published for all platform users through RAUM Support. Public templates follow the same inheritance rules as team templates.

Unpublish — Unpublishing a template prevents new child workspaces from being created. Existing child workspaces remain linked according to their inheritance state.

Delete a Template

 
To delete a template workspace use the delete function on the templates dashboard, Owner role required.

Please note that templates can only be deleted when no child workspaces exist. If a template still has child workspaces, deletion is blocked to prevent breaking dependent workspaces.

Limitations

Team Files — Templates cannot use team files or other external data. All required content must be stored inside the template workspace.

Access — Templates are only accessible to Owners and Admins. Users with lower roles cannot see templates in their workspace list and cannot be accessed otherwise.

Wormholes — Wormholes cannot be used on templates or created from within templates. They are only available in regular workspaces and in child workspaces based on a template.

Please note that Child workspaces can use team files; however, we do not recommend designing setups that rely on a combination of templates and team files, as this introduces dependencies outside the template’s control and significantly increases complexity.

links