> ## Documentation Index
> Fetch the complete documentation index at: https://learn.biq.li/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand built-in workspace roles

> Compare the Workspace Admin, Editor, and Member roles.

Biqli provides Admin, Editor, and Member roles for common collaboration needs.

* **Admin** is intended for broad workspace and resource administration.
* **Editor** is intended for creating and maintaining content without full administrative control.
* **Member** is intended for more limited day-to-day access.

The permissions shown in the role editor are the authoritative details. Review them before assignment, especially for billing, member management, deletion, and developer settings.

## Select a built-in role

Use **Admin** for people who genuinely need broad workspace administration. Use
**Editor** for people responsible for creating and maintaining resources. Use
**Member** for narrower routine participation.

Built-in labels describe intended use, but the current permission summary in
the dashboard is authoritative. Product and plan capabilities can affect what
an otherwise permitted member can do.

## Review sensitive actions separately

Link write access does not automatically mean ownership, billing, SSO, API-key,
or member-management access. Verify those categories before assigning a role to
a contractor, agency, or temporary teammate.

When a built-in role is close but not appropriate, create a reusable custom
role instead of granting excess access.

## Frequently asked questions

### Is Editor the same as Admin?

No. Editor is intended for content management without every administrative
capability. Review the current permission summary before assignment.

### Can the plan restrict a permitted action?

Yes. A role can allow a feature while the current workspace plan or quota does
not include it.