Roles and feature access

Understand workspace roles, project roles, plan gates, and why two users may see different Cleo navigation.

Cleo access is determined by a combination of workspace membership, project assignment, role, site plan, and site-specific capabilities.

Workspace roles

• Admin manages workspace-level membership and broader account settings.
• Member uses the clients and sites assigned to them.

Project roles

Role	Typical access
Owner	Full control of the project, including member access and high-impact actions.
Editor	Run tools, create and change work, and use supported publishing actions.
Viewer	Read dashboards and reports without changing the site or starting chargeable work.

Exact permissions can vary by feature. Cleo checks permission again on the server for protected actions.

Why a feature is missing or locked

• The site plan does not include it.
• The feature has not been enabled for that site.
• Your project role does not permit the action.
• A required integration or onboarding step is incomplete.
• The feature is in a limited beta.
• The site uses a different platform workflow.

Diagnose access

1. Confirm you opened the correct client and site.
2. Refresh after accepting an invitation or changing roles.
3. Check Plans & Billing for module access and usage.
4. Ask an Admin or project Owner to confirm your assignment.
5. If the expected access still does not appear, contact [e-mail] with the workspace, client, site, and feature name.

When reporting an access problem, describe what you see—hidden navigation, a lock, an access-denied page, or a disabled action. These usually have different causes.