Role-Based Access Control
Role-Based Access Control (RBAC) lets you configure fine-grained user access in Panther.
A role is a configurable set of permissions, and each user is assigned to one role. You can use the default roles provided, customize them to your needs, and/or create new roles. For certain permissions, you can restrict accessible log types. It is possible to create a role with no permissions.
You can manage roles in your Panther Console or with the Panther REST API or GraphQL API.
Panther user roles
Default Panther roles
When you first deploy Panther, the following three roles are automatically created for you:
AdminThis role is automatically assigned to all existing users and has all available permissions.
AnalystThis role can use all the cloud security and log analysis features, but cannot modify settings.
AnalystReadOnlyThis role can view resources and alerts and Python code, but cannot change anything.
Important details about the Admin role:
A user with the
Adminrole cannot downgrade themselves to a non-Adminrole. Only anotherAdminuser can downgrade their role on their behalf.Only a user with the
Adminrole can delete other users with theAdminrole. Self-deletions are not supported.At least one password-based user must have the
Adminrole.If Enforce Single Sign On (SSO) is enabled, at least one IdP-managed user must also have the
Adminrole, in addition to at least one password-based user with theAdminrole.

Customizing roles
A user assigned to a role that has the Manage Users permission (or UserModify, if created through the API) can customize all other roles.
There is no limit on the number of roles you can create.
You can rename roles, but all roles must have unique names.
You can change permissions on roles, but at least one user must have the Manage Users/
UserModifypermission.You can delete a role if no users are currently assigned to it.

For instructions on customizing a role with restrictions on certain log types, see the RBAC per log type section below.
Permission names in the Console and API
AI Run As
AIRunAsModify
Configure which user or API token AI automations (auto-triage, scheduled prompts) execute as
Bulk Upload
BulkUpload
Allow bulk upload of both policies and rules
Bulk Upload Validate
BulkUploadValidate
Allow a bulk upload to be validated
Manage AI Responses
ManageAIResponses
Edit/delete any user's AI responses
Manage Alerts
AlertModify
Read + update, add, and delete alerts
Manage API Tokens
OrganizationAPITokenModify
List/describe + create, modify, delete Panther API tokens
Manage Cloud Security Sources
CloudsecSourceModify
Read + add, delete, and modify cloud security integrations
Manage Log Sources
LogSourceModify
Read + add, delete, and modify log analysis integrations
Manage Policies
PolicyModify
Read + update, add, and delete policies
Manage Rules
RuleModify
Read + update, add, and delete rules
Manage Saved Searches
DataAnalyticsModify
Creates and updates saved queries
Manage Scheduled Prompts
ManageScheduledPrompts
Create, edit, delete, toggle, and bulk-import AI scheduled prompts
Manage Users
UserModify
List + invite, delete, and modify users & their roles
Query Data Lake
DataAnalyticsRead
Run queries over historical data
Read Alerts
AlertRead
View alerts
Read API Token Info
OrganizationAPITokenRead
List/describe all Panther API tokens
Read Panther Settings Info
GeneralSettingsRead
View basic settings like error reporting and org name
Read User Info
UserRead
List all Panther users & available roles
Run Panther AI
RunPantherAI
Use Panther AI
View AI Private Responses
ViewAIPrivateResponses
View all users' private AI responses
View Cloud Security Sources
CloudsecSourceRead
View list of cloud security integrations and their configurations
View Log Sources
LogSourceRead
View list of log analysis integrations and their configurations
View Overview
SummaryRead
Fetch summary data for the overview dashboards
View Policies
PolicyRead
View policies and their compliance status
View Rules
RuleRead
View rules
View Scheduled Prompts
ViewScheduledPrompts
View AI scheduled prompts and their run history, and download them as YAML
Updating a role's permissions
To update the permissions associated to a role:
At the bottom of the left-hand navigation bar in your Panther Console, click Settings, then navigate to Access & Authentication > Roles & Permissions.
In the upper-right corner of the tile for the role you'd like to update, click the three docs icon > Edit.

Make desired changes to the permissions set.
Click Update Role.
Permission changes will not take effect until the affected user refreshes the browser where they are logged in to Panther or signs out and back in to Panther.
If, after expanding a user's permissions, the user continues to see an access denied error, verify they have the required read permission for the page they're attempting to access.
Creating a new role
Follow the instructions below to create a new role in the Console. Alternatively, you can create a new role using the Panther GraphQL API or REST API.
At the bottom of the left-hand navigation bar in the Panther Console, click Settings, then navigate to Access & Authentication > Roles & Permissions.
Click Create New.
In the Name field, enter a descriptive name for the role.
Select the checkbox for each of the permissions you'd like this role to have.
Currently, some permissions support log type filtering. (See RBAC per log type for more information.) If you select a permission that supports log type restrictions, choose one of the following options:
Full access to logs
Allow access to selected Log Types
Deny access to selected Log Types

If you opted to Allow access to selected Log Types or Deny access to selected Log Types, in the Select Log Types dropdown, select the individual log types the user should be allowed to access or restricted from accessing.
Be sure to read through the limitations listed below to understand the current limitations of the RBAC by log type feature.
Remember that log type selections sync across all permissions that support log type restrictions, for a given role.
Click Create Role.
Note that it may take a up to one minute for your change to propagate across all of Panther's services.
You can now assign the role to users you onboard onto Panther.
RBAC per log type
While this feature is available to all customers with Snowflake Enterprise Edition, Panther must first enable it for your instance. If you are interested in using it, please reach out to your account team. This feature is currently not compatible with a Databricks backend.
Prerequisites for Cloud Connected Snowflake accounts
If you're using a Cloud Connected Snowflake instance, in order to enable RBAC per log type, the following must be true:
Your Snowflake edition must be Enterprise or higher.
The
pantheraccountadminuser account must be enabled in your Snowflake instance. If it is not already enabled, follow the instructions in Snowflake's Enabling a User documentation.
How to restrict log types for a certain role
You can create a new role and restrict log access for it, or alter the permissions of an existing role to restrict log access. See the Creating a new role instructions, paying attention to Step 4.
RBAC per log type for search
You can use the Run Log Queries permission to limit a role's log type access in Panther's search tools, including Data Explorer and Search.
In Data Explorer, only tables for the log types the user has access to will display in the Data Explorer filter list, as well as in predictive text in the SQL editor.
When pivoting into Data Explorer from another area of the Console (such as from a log source's Schemas view), if the filled SQL query references a table for a log source the user does not have access to, upon running the query, the user will receive an error.
In Search, database tables for restricted log types will not populate in the tables filter.
Limitations for RBAC per log type for search
Note the following limitations when RBAC per log type for search is applied to a role:
Alerts: This feature does not currently enforce RBAC per log type restrictions in alerts or, and therefore blocks users from viewing/managing them (unless the RBAC per log type for alerts feature is enabled).
The following permissions may not be enabled: View Alerts, Manage Alerts.
Detections: The Manage Rules and Manage Policies permissions may not be enabled.
The View Rules and View Policies permissions may be enabled.
Cloud Security data: Only users with full access to all log types will be able to view Cloud Security data in the
panther_cloudsecuritydatabase and thepanther_views.public.all_cloudsecurityview in Snowflake.All other Cloud Security data (resources, compliance) in the Console (e.g., on the Overview and Detections pages) will be available to all users.
Saved Searches: Users with restricted access cannot create Saved Searches (nor view Saved Searches).
Scheduled Searches: If a user with a role with full log type access has Scheduled Searches and is then switched to a role with restricted log type access (or their same role is modified to restrict log type access), their Scheduled Searches will stop running.
Lookup Tables: A user with a restricted role will not be able to query Lookup Tables in Data Explorer or Search.
External tables: Queries to external (non Panther-created) tables will only function for users with access to all log types.
API Tokens: This feature does not support API tokens. All API tokens have full access to the data lake and Saved Searches.
RBAC per log type for alerts
You can use the View Alerts and Manage Alerts permissions to limit a role's access to alerts based on log type. When selecting either of these permissions, you will be prompted to select the log types to allow or restrict access to.
The set of accessible log types selected for View Alerts and Manage Alerts will be synced with the Run Log Queries permission. One role cannot have two permissions with different log type restrictions.
All limitations for RBAC per log type for search, listed above, apply—except for the alerts limitation.
AI-related permissions
Panther includes several AI-related permissions that control access to Panther AI features:
Run Panther AI
The Run Panther AI permission allows users to interact with Panther AI features, including:
Starting AI conversations and asking questions
Running AI alert triage on demand
Viewing scheduled AI prompts
Accessing AI-powered analysis and recommendations
AI Run As
The AI Run As permission is an administrative permission that allows users to configure run-as user settings for AI automations. Users with this permission can:
Configure scheduled prompts to run as a specific user or API token instead of the prompt creator
Configure auto-run AI alert triage to run as a specific user or API token instead of using system-level permissions
Specify which user account's permissions and data access should be used for automated AI executions
The AI Run As permission automatically implies Run Panther AI. Users with AI Run As are automatically granted Run Panther AI.
View Scheduled Prompts
The View Scheduled Prompts permission allows users to view scheduled AI prompts and their run history, and to download prompts as YAML. It is included in the default Admin, Analyst, and AnalystReadOnly roles, because Run Panther AI implies it.
Viewing a prompt does not allow creating, editing, or deleting it — that requires Manage Scheduled Prompts.
Manage Scheduled Prompts
The Manage Scheduled Prompts permission allows users to create, edit, delete, enable/disable, and bulk-import scheduled AI prompts (including via bulk upload of YAML files). It is included in the default Admin role only.
As of Panther 1.127, managing scheduled prompts is decoupled from Run Panther AI and requires the separate Manage Scheduled Prompts permission. This permission is not automatically granted to non-Admin roles.
Run Panther AI still implies View Scheduled Prompts (read access), but custom roles with only Run Panther AI cannot create, edit, delete, or import prompts until an admin grants Manage Scheduled Prompts.
Last updated
Was this helpful?

