> For the complete documentation index, see [llms.txt](https://docs.cybaops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybaops.com/settings/user-roles.md).

# User Roles

CybaOps uses **role-based access** to ensure customers and partners can securely manage their own environments while maintaining clear boundaries between operational, commercial, and administrative responsibilities. 

Roles differ depending on whether you are working in an **End Client tenancy** or a **Partner tenancy**. 

### <mark style="color:$primary;">End Client Tenancy Roles</mark>

End Client tenancies are used by organisations to manage their own cyber security posture, compliance activity, and operational visibility within CybaOps.

#### <mark style="color:$primary;">Admin</mark>

The **Admin** role is responsible for the overall configuration and management of the client’s CybaOps tenancy.

**Admins can:**&#x20;

* Add, remove, and manage users within the client tenancy&#x20;
* Control platform settings such as notifications and integrations&#x20;
* Assign appropriate access to internal team members&#x20;
* Oversee security, compliance, and operational modules enabled for the organisation&#x20;

This role is usually assigned to:&#x20;

* IT Managers&#x20;
* Security Leads&#x20;
* Compliance Owners&#x20;
* Senior technical stakeholders&#x20;

The Admin role aligns with management-level permissions within CybaOps tenants as defined in internal service role documentation

#### <mark style="color:$primary;">User</mark>

The **User** role is a **view only** role designed for day‑to‑day platform usage without administrative control.

**Users can typically:**&#x20;

* View dashboards, insights, and reports relevant to their organisation&#x20;
* View with enabled modules (e.g. assessments, vulnerability views, incident tracking)&#x20;

This role is suitable for:&#x20;

* Operational staff&#x20;
* Compliance contributors&#x20;
* Wider IT teams needing visibility rather than control&#x20;

Users **cannot** take actions such as comments or answer questions on assessments.

### <mark style="color:$primary;">Partner Tenancy Roles</mark>

Partner tenancies are used by MSPs, resellers, and internal commercial teams to manage multiple customer environments and commercial activity within CybaOps.

#### <mark style="color:$primary;">Admin (Partner Admin)</mark>

The **Admin** role in the partner tenancy has full control over the partner tenancy.

**Partner Admins can typically:**&#x20;

* Manage partner users (including Sales users)&#x20;
* Create and manage client tenancies&#x20;
* Configure partner-level settings and branding&#x20;
* View and manage all customers linked to the partner account&#x20;
* View security related information within the partner tenancy

This role is usually held by:&#x20;

* Partner owners&#x20;
* Partner operations managers&#x20;

Partner Admin capabilities are directly referenced in CybaOps partner documentation and onboarding flows.

#### <mark style="color:$primary;">Sales</mark>

The **Sales** role is designed for commercial and pre‑sales activity without operational or technical control.

**Sales users can typically:**&#x20;

* View assigned customer tenancies&#x20;
* Support commercial conversations without accessing sensitive configuration or security settings&#x20;

This role enables sales teams to remain informed with their client tenancies, with out risking mistakes on internal security settings.

### <mark style="color:$primary;">Summary Table</mark>

<table><thead><tr><th width="141">Tenancy Type</th><th width="94">Role</th><th>Primary Purpose</th></tr></thead><tbody><tr><td>End Client</td><td>Admin</td><td>Full control of the client's CybaOps tenancy</td></tr><tr><td>End Client</td><td>User</td><td>Day to day usage and visibility</td></tr><tr><td>Partner</td><td>Admin</td><td>Full control of partner and customer management</td></tr><tr><td>Partner</td><td>Sales</td><td>Commercial visibility</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cybaops.com/settings/user-roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.