---
title: View permissions for a user
description: Use Access Analyzer to view permissions for a selected user.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/access-control/view-permissions-for-a-user.html
release: australia
product: Access Control
classification: access-control
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 2
breadcrumb: [Using Evaluate access, Using Access Analyzer, Access Analyzer, Access Management]
---
# View permissions for a user
Use Access Analyzer to view permissions for a selected user.
## Before you begin
Role required: access\_analyzer\_admin
This procedure explains how to view the permissions for a specific user \(such as **ITIL User**\) on the **Incident** table by using the Evaluate Access feature in Access Analyzer.
**Note:** Access Analyzer is a ServiceNow AI Platform Store product.
## Procedure
1. Navigate to **All** > **Access Analyzer** > **Analyze Permissions**.
The Analyze access and permissions homepage is displayed.
2. Select your criteria as follows:
|
Field
|
Description
|
|---|
|
Analyze by \*
|
Select **User**.
|
|
Select user \*
|
Specify a user name to select from the list. In this example, **ITIL User**.
|
|
Rule type \*
|
Analyze access for the following:- Table
- UI page
- REST Endpoint
- Client callable script include
- AI Agent
- Agentic workflow.
In the example, `Table`
.
|
|
Select table \*
|
Specify a table name to select from the list. In this example, **Incident**.
|
|
Select record
|
Specify a record name to select from the list. In this example, **INC0000001**.
|
|
Select field
|
Specify a field name to select from the list. This field can be used to analyze permissions even at the field level. For example, Active, Created By, and so on.
|
3. Specify the description in the **Description** field.
4. Click **Analyze permissions**.
\[Omitted image "view-permissions-for-a-user.png"\] Alt text: Permission evaluation of Abel Tuter
The system displays **Access results** for the **ITIL User**.
\[Omitted image "permissions-for-a-user.png"\] Alt text: Permission results
The results can be read by referring to the Legends, access control list \(ACL\), IAccesshandler, and Data filters.
Let's take the example of **read** operation. For the **ITIL User** overall access is Passed, which means the user is able to read the record with the correct permissions \(ACL\).
Similarly for **create** operation, the overall access is passed with an alert icon, which means that there could be a presence of script for the ACL evaluation.
**Note:** In the example, **write** and **delete** operations are blocked for the selected user and the user can’t edit or delete the selected record \(INC0000001\).
5. Select read operation to know more about the Debug logs.
\[Omitted image "acl-details-for-user.png"\] Alt text: ACL Details
The Debug logs page displayed the business rule and associated ACLs that are required to perform the **read** operation for the record.
The Debug logs shows that there’s a business rule and four ACLs associated for the read operation.
There’s a status **Passed** for one of the ACL, which means to read the selected record, the user has the required ACL and can read the record. Since one of the ACL is **Passed**, the other ACL evaluations are **Skipped**.
6. Select the Access Control that is Passed to see the details of the ACL.
\[Omitted image "view-details-for-a-user.png"\] Alt text: Details of the Access Control for the selected ACL
The system displays the Access Control details for the selected ACL.
If a selected operation that has `Passed` contains a script, the Access Control page displays the associated script for the record.
\[Omitted image "script-for-a-user.png"\] Alt text: Script Condition in Access Control