> 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/logs/access-controls.md).

# Access Controls

Understand how to safeguard log data that may contain sensitive information through permission sets and data masking.

Log data captured by Pharos can contain sensitive information from your Salesforce organization. Stack traces, error messages, and debug logs may expose object names, field values, user information, and other potentially confidential data. Implementing proper access controls ensures that only authorized users can view and interact with this information.

{% hint style="warning" %}
**Defense in Depth:** Pharos provides two complementary layers of protection—permission sets control who can access logs, and data masking automatically redacts sensitive field values before they're stored.
{% endhint %}

## How Pharos Protects Log Data

Pharos provides a comprehensive access control system built on two complementary approaches:

| Protection Layer    | What It Does                                                    | Best For                                                                                   |
| ------------------- | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **Permission Sets** | Control who can access Pharos and what actions they can perform | Role-based access: read-only monitoring vs. full investigation vs. platform administration |
| **Data Masking**    | Automatically redact sensitive field values before storage      | PII, SSNs, credit cards, and other sensitive data types                                    |

**Permission Model:** Designed to align with common organizational structures—development teams get full access for investigations, business stakeholders get visibility into trends, and integration users get elevated permissions for automated workflows.

{% hint style="info" %}
**Separate Distribution:** Pharos permission sets (`Log_Read`, `Log_Read_Write`, `Log_Admin`) are not part of the 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. Deploy `pharos-permissions` to your org, then assign the permission sets as described below.
{% endhint %}

## 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 providing tiered access, from read-only monitoring to full administration.</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>🎭 Data Masking</strong></td><td>Redact sensitive field values like SSNs and PII from logs before they're stored.</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>
