> 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/org-insights/security.md).

# Security

Review dashboards in the Security tab for sensitive permission analysis, user access patterns, and risk identification.

The Security tab surfaces permission-related risks that are otherwise buried across profiles, permission sets, and role hierarchies in Salesforce Setup. Instead of clicking through dozens of profile pages to understand who has access to what, you get a consolidated view of sensitive permissions and the users who hold them.

***

## Sensitive Permissions

At the core of the Security tab is an analysis of **sensitive system permissions**—the high-impact permissions that can significantly affect data access and org configuration.

Pharos identifies the permissions that carry the most risk and shows you exactly how many users hold each one.

| Permission          | Risk   | Why It Matters                                                         |
| ------------------- | ------ | ---------------------------------------------------------------------- |
| **View All Data**   | High   | Bypasses all sharing rules—user can see every record in the org        |
| **Modify All Data** | High   | Full read/write access to all records regardless of sharing            |
| **Manage Roles**    | Medium | Can restructure the role hierarchy, affecting data visibility org-wide |
| **Reset Passwords** | Medium | Can reset other users' passwords, enabling account takeover            |
| **Manage Sharing**  | Medium | Can alter sharing rules that govern record access                      |

{% hint style="warning" %}
**Common Finding:** It's not unusual to discover that 20+ users have View All Data permissions in an org, many of whom don't actually need that level of access. Permission bloat tends to accumulate over time as roles shift and temporary access grants become permanent.
{% endhint %}

The permission overview gives you a quick count: for each sensitive permission, how many users currently hold it? This alone is often eye-opening—particularly for permissions like **Reset Passwords** or **Manage Roles** that tend to be granted broadly and forgotten.

***

## User-Level Analysis

Beyond aggregate counts, the Security tab lets you drill into individual users to understand their complete permission profile.

For each user, Pharos shows:

| Detail                  | Description                                                                                                                                       |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Permission Source**   | Whether a permission comes from the user's profile or a specific permission set                                                                   |
| **Risk Classification** | Users are classified based on the cumulative sensitivity of their permissions                                                                     |
| **Persona Detection**   | Pharos identifies when a user's actual permissions exceed what their role suggests—for example, a standard user who holds admin-level permissions |

This is particularly useful when you encounter a user who shouldn't be a System Administrator but effectively has equivalent access through a combination of permission sets. The Security tab makes this visible without requiring you to manually cross-reference profiles and permission set assignments.

{% hint style="info" %}
**Persona vs. Profile:** A user might have a "Standard User" profile but hold permission sets that collectively grant admin-level access. Pharos detects this gap and flags it, so you can evaluate whether the access is intentional or an oversight.
{% endhint %}

***

## Permission Browser

The permission browser provides a detailed, navigable view of permissions at the user level. Rather than the flat list you get in Salesforce Setup, permissions are organized by source and severity.

This view answers questions like:

* Why does this SDR have Modify All Data?
* Which permission set granted View Setup Configuration to this marketing user?
* How many sensitive permissions does this service account hold?

The browser makes it straightforward to trace a permission back to its origin—whether it was assigned through a profile, a permission set, or a permission set group. That traceability is essential for cleanup efforts, because you need to know where to revoke access without breaking other assignments.

***

## Practical Use Cases

The Security tab is most valuable during periodic access reviews and in response to security events. Here are common scenarios where it delivers immediate value.

### Access Audits

When compliance requires a review of who has access to sensitive data, the Security tab replaces the manual process of exporting permission set assignments and cross-referencing them in spreadsheets.

### New Hire / Departure

When someone joins or leaves the team, the user-level analysis makes it easy to verify that permissions are appropriate for their role—or that access has been fully revoked.

### Incident Response

If a security concern arises, the sensitive permissions overview immediately shows which accounts have the access level that could be involved.

{% hint style="info" %}
**Evolving Capability:** The Security tab is actively being enhanced. Future iterations will include deeper OAuth token analysis, connected app visibility, and integration with Salesforce Health Score recommendations—expanding from permission analysis into a more comprehensive security posture view.
{% endhint %}

***

## Taking Action

The insights from the Security tab translate directly into concrete steps.

| Finding                                               | Recommended Action                                                      |
| ----------------------------------------------------- | ----------------------------------------------------------------------- |
| Users with View All Data who don't need it            | Remove the permission or replace with more targeted object-level access |
| Inactive users holding sensitive permissions          | Deactivate the user account and reclaim the license                     |
| Permissions granted via profile that should be scoped | Migrate to permission sets for more granular control                    |
| Service accounts with broad access                    | Review whether API integrations truly require the assigned permissions  |

{% hint style="success" %}
**Next Steps:** For a view of how automation complexity maps to your org's objects, visit the [Automation](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/org-insights/automation.md) tab. To review overall org health metrics, see [Org Overview](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/org-insights/org-overview.md).
{% endhint %}
