Permissions matrix

This table shows what each role can do. Read down a column to see the permissions for a role, or across a row to see which roles can perform an action.

• User: anyone with access; sees and does only what they’ve been granted, per collection.
• Approver: a user who has also been granted Approve, and works the Review queue.
• Collection Admin: a user granted admin on a single collection.
• Library Admin: manages the whole library except billing and deletion.
• Library Owner: the highest-level role, with full library access including billing and library deletion.

A check mark means the capability is granted. A blank cell means it is not.

Capability	User	Approver	Collection Admin	Library Admin	Library Owner
View / Download	✓	✓	✓	✓	✓
Create content	✓	✓	✓	✓	✓
Edit content	✓	✓	✓	✓	✓
Move / organize	✓	✓	✓	✓	✓
Delete	✓	✓	✓	✓	✓
Approve / Reject		✓	✓	✓	✓
Override check-out (unlock)			✓	✓	✓
Assign users to a collection			✓	✓	✓
Edit permissions			✓	✓	✓
Invite / remove users				✓	✓
Manage groups				✓	✓
Configure taxonomy & settings				✓	✓
Manage billing / subscription					✓
Delete library					✓

Note

Capabilities are ultimately granted per collection, usually through groups. The User and Approver columns therefore show what’s possible when granted: a user with no grant in a collection can’t see it at all, while a user granted the right capabilities can create, edit, move, or delete there. Granting a user Approve is exactly what makes them an approver.

Note

Collection Admin permissions apply only to the collection that person administers and do not extend across the library. Manage billing / subscription and Delete library are Library Owner only.

Related

• Roles & access, each role explained in plain terms.
• Users, groups & permissions: the full model behind this table.
• Onboard users & permissions: how to grant this access.