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

# Permissions

Detailed information about the three permission sets included with Pharos and their appropriate use cases.

Pharos includes three permission sets designed to support different user roles and access requirements within your organization. Each permission set provides a specific level of access to the platform, allowing you to grant appropriate capabilities based on how users need to interact with log data and issue tracking features.

{% 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`, `ManageDataIntegrations`) that Salesforce does not allow inside a managed package. You deploy `pharos-permissions` to your org separately, after installing Pharos.
{% endhint %}

## Log\_Read (Read-Only Access)

The **Log\_Read** permission set is designed for users who need to monitor and review system activity without making any modifications. This permission set provides read-only access to logs and issues.

Users with this permission set can view error trends, examine stack traces, review impact statistics, and explore issue details. They can access charts and dashboards, run searches across log data, and investigate the relationships between logs and issues. However, they cannot create or modify issues, initiate traces, or trigger AI analysis.

This permission set is ideal for business stakeholders, product managers, and team members who need visibility into application health and error patterns but don't actively participate in debugging and resolution activities. It's also useful for audit purposes, allowing management to review system activity without inadvertently modifying data.

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

The **Log\_Read\_Write** permission set provides edit access to logs and issues, enabling users to actively investigate issues and leverage all platform features. In addition to everything available in Log\_Read, users with this permission set can create and edit issues, modify issue priorities and assignments, mark issues as resolved or duplicate, and add comments and descriptions.

This permission set also enables users to initiate debug tracing on specific components and trigger AI-powered analysis of issues. These capabilities make it the appropriate choice for developers, DevOps engineers, support personnel, and anyone actively involved in investigating and resolving application issues.

Log\_Read\_Write includes access to all the interactive features that help teams collaborate on issue resolution while maintaining read access to the complete historical record of logs and issues.

## Log\_Admin (Full Administrative Access)

The **Log\_Admin** permission set provides the comprehensive access required for Pharos to operate properly and for administrators to configure the platform. This permission set is essential for the platform to function and should be assigned to the user account under which Pharos executes its automated processes—the [Pharos running user](https://docs.pharos.ai/configuration-guide/the-basics/pharos-running-user.md)—as well as to administrators responsible for configuring and managing the platform.

### Required for Platform Operation

Pharos requires the Log\_Admin permission set to perform several critical functions. The platform needs to process platform events, execute batch jobs for log processing and issue tracking, fetch deployment metadata from your Salesforce organization, access event log files for monitoring capabilities, and interact with various Salesforce APIs to provide its observability features.

Without Log\_Admin assigned to the appropriate user or integration account, Pharos cannot execute these background operations, which will result in incomplete log data, missing issue tracking functionality, and degraded platform performance.

**User permissions granted:** AuthorApex, CustomizeApplication, ManageCustomPermissions, ManageDataIntegrations, ManageInteraction, ModifyMetadata, ViewAllData, ViewDataLeakageEvents, ViewEventLogFiles, ViewPlatformEvents, ViewPublicDashboards, ViewPublicReports, ViewRoles, ViewSetup.

### Understanding ViewAllData and Elevated Permissions

Log\_Admin includes several Salesforce system permissions that often raise security questions, particularly the ViewAllData permission. Organizations understandably scrutinize this permission due to its broad scope and potential security implications. However, these permissions are required for specific technical reasons related to how Salesforce's APIs function.

The ViewAllData permission is primarily required by Salesforce's metadata API to fetch deployment results and change information. Salesforce requires this permission for certain metadata operations, even though Pharos only needs access to deployment history and metadata details—not the actual data within your organization's records. This is a Salesforce platform requirement, not a design choice in Pharos.

Similarly, permissions like ViewEventLogFiles and ViewPlatformEvents are required to access Salesforce's event monitoring data, which Pharos uses to provide insights into governor limit consumption, API usage patterns, and system performance metrics.

### Data Access Practices

It's important to understand that while Log\_Admin grants these technical capabilities, Pharos does not access or examine the data within your organization's standard or custom objects. The platform operates exclusively with its own custom objects for logs, issues, and related tracking data.

When Pharos identifies related records referenced in error messages or stack traces, it only captures the record ID and object type. For example, if an error occurs while processing an Account record, Pharos will note that an Account with a specific ID was involved, but it does not read or store any field values from that Account record. This approach provides the context needed for debugging while respecting data boundaries.

The platform never queries your business data, never stores copies of your records, and never transmits your organization's data outside of the standard Pharos objects. The elevated permissions exist solely to support the technical operations required for log processing, metadata access, and platform functionality.

### Assignment Recommendations

Log\_Admin should be assigned to:

* The integration user or service account under which Pharos executes (required)
* Platform administrators responsible for configuring Pharos settings and integrations
* System administrators who need to troubleshoot platform functionality

This permission set should not be assigned to general users, even those actively working with logs and issues. Log\_Read\_Write provides all the capabilities needed for day-to-day debugging and issue resolution activities.

## Selecting the Right Permission Set

When assigning permission sets to your users, consider their role and how they'll interact with Pharos. Users who need to investigate and resolve issues should receive Log\_Read\_Write access. Those who need to monitor error trends and review impact statistics without making changes should receive Log\_Read access. Log\_Admin should be reserved for the platform's integration account and administrators who need to configure platform settings.

You can assign permission sets through Salesforce's standard permission set assignment process, either individually or as part of permission set groups to manage access at scale. Remember that Log\_Admin is required for Pharos to function properly, so ensure it's assigned to the appropriate integration account during initial setup. Since these permission sets ship via the `pharos-permissions` download rather than the managed package, make sure it has been deployed to your org before assigning them.
