Skip to main content

How Access Works in Unplex: Roles, Seats, and Sharing

Reference overview of the four independent access levels in Unplex — account role, seat, project role, and assistant/template sharing — and how they interact.

Written by Sabina Sokolowski

1. Overview

Access in Unplex is determined at four independent levels, from the whole workspace down to a single project. Each level is set separately; access at one level does not imply access at another.

2. The Four Levels of Access

Level

Controls

Values

Account role

Permissions across the whole workspace

Owner, Admin, Member

Seat

Whether the product can be used at all

Assigned / none

Project role

Permissions inside a specific project

Owner, Editor, Viewer

Assistant / template sharing

Whether the wider team can use an item created by one member

Private / Shared

2.1 Account Role

The account role is Owner, Admin, or Member. The Owner is the single accountable party for the workspace and holds two exclusive capabilities: deleting the workspace and transferring ownership. Admins hold every other workspace-wide capability. Members use the product within their own and shared projects.

See Account Roles: Owner, Admin, and Member.

2.2 Seat

A seat is a named licence, independent of account role. Without an assigned seat, no product access is possible regardless of role. Seats are assigned by Owners and Admins, up to the workspace plan's limit.

See Managing Seats and Licences.

2.3 Project Role

Inside a project, a member holds the role of Owner, Editor, or Viewer, independent of their account role — a Member can be the Owner of a project. All content within a project (chats, matrices, notes) inherits the project's access setting automatically.

See Project Roles: Owner, Editor, and Viewer.

2.4 Assistant and Template Sharing

An assistant or template created by a member is Private by default until explicitly shared with the team. A Shared item can be used and duplicated by colleagues; only the original creator can edit the source item.

See Sharing Assistants and Templates.

3. Interaction Between Levels

The four levels are set independently, so access at any given point is exactly the sum of what has been explicitly granted. Example: a workspace Member (account role) holding a seat (product access) can simultaneously be the Owner of a project they created, an Editor on a colleague's project, a Viewer on a third, and have one shared assistant available to the whole team.

4. Related Task Articles

This article covers the underlying concepts. For step-by-step instructions, see:

Did this answer your question?