> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/access-controls.md).

# Access Controls

Control issue access and understand permission requirements.

Issues aggregate error data—stack traces, impacted users, related records—that may contain sensitive information. Access controls ensure only authorized users can view and manage Issues.

***

## How Pharos Protects Issue Data

Pharos uses **permission sets** to control who can access Issues and what actions they can perform:

| Permission Set       | Access Level | Typical Roles                                     |
| -------------------- | ------------ | ------------------------------------------------- |
| **Log\_Read**        | Read-only    | Business stakeholders, product managers, auditors |
| **Log\_Read\_Write** | Read-write   | Developers, DevOps, support, triage               |
| **Log\_Admin**       | Full admin   | Integration user, platform administrators         |

{% hint style="info" %}
**Separate Distribution:** These permission sets are not part of the Pharos managed package. They ship separately as the downloadable [pharos-permissions](https://resources.pharos.ai/pharos-permissions) ZIP file because they include application-level user permissions (e.g., `CustomizeApplication`, `ModifyMetadata`, `AuthorApex`) that Salesforce does not allow inside a managed package.
{% endhint %}

***

## Permission Model

* **Log\_Read** — View Issues, logs, impact stats; no create/edit/delete
* **Log\_Read\_Write** — Full issue management: triage, status updates, ticket creation, tracing, AI analysis
* **Log\_Admin** — Required for Pharos background operations; assign to integration user and admins only

***

## Explore Access Controls

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>🔑 Permissions</strong></td><td>Three permission sets, and why write permission is recommended for issue management.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/access-controls/permissions.md">Permissions</a></td></tr></tbody></table>

***

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>🔐 Logs Access Controls</strong></td><td>Log-level permissions and data masking</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/access-controls.md">Access Controls</a></td></tr><tr><td><strong>🎭 Data Masking</strong></td><td>Sensitive data in logs</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/access-controls/data-masking.md">Data Masking</a></td></tr></tbody></table>
