Roles in Spaces

A Space has three roles: Space Admin, Space Editor and Space Viewer. They control what a member can do inside that one Space, and they’re separate from the organization-level roles that decide what you can do across the platform.

The three Space roles

Space Admin

The highest permission level in a specific Space. A Space Admin decides the Space’s security classification, administers its members, and can create and edit any assistant in it.

Space Editor

Can create and edit assistants, and connect knowledge, in this Space specifically — without needing the organization-level Creator role. A Space Editor can’t administer members, change the Space’s security classification, or invite new members; and an assistant they publish requires approval from a Space Admin before it becomes available to everyone in the Space.

Space Viewer

An end user of the Space. A Space Viewer can use assistants published in it, but can’t change any settings or create new ones. Anyone with the organization-level User role automatically becomes a Viewer in the Spaces they’re added to.

How Space roles relate to organization roles

Organization roles — User, Creator, Admin — decide what you can do across the whole platform. Space roles decide what you can do inside one specific Space. The two combine. An organization User is always at least a Viewer in any Space they’re added to — but a Space Admin can grant someone Editor or Admin rights in their own Space, regardless of that person’s organization-level role. See Roles in Intric for the complete picture.

Why delegate with Space Editor

Assign the Space Editor role when you want a subject-matter expert to build assistants for their own team’s Space — an HR specialist creating a policy assistant in the HR Space, for example. It keeps membership and final publication under the Space Admin’s control.