> 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/permissions.md).

# Permissions

Learn about the three permission sets and why write permission is recommended for issue management.

Pharos includes three permission sets that control access to Issues (and logs). Assign the appropriate set based on each user's role. This page looks at what each one means for issue work specifically; [Permissions](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/access-controls/permissions.md) covers the permission model itself, including why the sets ship separately from the managed package and how to deploy them.

***

## Log\_Read (Read-Only)

**For:** Business stakeholders, product managers, auditors, anyone who monitors but doesn't fix.

| Can                             | Cannot                                      |
| ------------------------------- | ------------------------------------------- |
| View Issues, logs, impact stats | Create or edit Issues                       |
| Run reports and dashboards      | Update status, priority, or assignment      |
| Search Issues and logs          | Add comments                                |
| View debug views, stack traces  | Initiate traces or AI analysis              |
|                                 | Create tickets or link to Jira/Azure DevOps |

***

## Log\_Read\_Write (Read-Write)

**For:** Developers, DevOps, support, triage—anyone actively investigating and resolving Issues.

| Can                                       | Why It Matters       |
| ----------------------------------------- | -------------------- |
| Everything in Log\_Read                   | Full visibility      |
| Create and edit Issues                    | Triage workflow      |
| Update status, priority, assignment       | Lifecycle management |
| Add comments, mark duplicates             | Collaboration        |
| Initiate traces                           | Debug log capture    |
| Trigger AI analysis                       | Faster root cause    |
| Create tickets, link to Jira/Azure DevOps | Escalation workflow  |

{% hint style="success" %}
**Recommended for triage:** Users who triage Issues need Log\_Read\_Write access to update status, assign priority, and add tickets. Log\_Read-only users cannot complete triage workflows.
{% endhint %}

***

## Log\_Admin (Full Administrative Access)

**For:** Integration user (Pharos running user), platform administrators.

| Can                              | Why It Matters                          |
| -------------------------------- | --------------------------------------- |
| Everything in Log\_Read\_Write   | Full platform access                    |
| Configure Pharos Admin settings  | Integrations, notifications, monitoring |
| Manage rules and automation      | Notification rules, ticketing rules     |
| Access event logs, metadata APIs | Required for platform operation         |

**Required for platform operation:** The integration user under which Pharos runs must have Log\_Admin. Without it, background jobs (log processing, issue fingerprinting, notifications) will not execute.

***

## Assignment Recommendations

| Role                            | Permission Set   |
| ------------------------------- | ---------------- |
| Integration user (running user) | Log\_Admin       |
| Platform administrators         | Log\_Admin       |
| Developers, triage, support     | Log\_Read\_Write |
| Product managers, stakeholders  | Log\_Read        |

***

## 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 Permissions</strong></td><td>Same permission sets for log access</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/access-controls/permissions.md">Permissions</a></td></tr><tr><td><strong>🔐 Access Controls</strong></td><td>Overview</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/access-controls.md">Access Controls</a></td></tr></tbody></table>
