| Type |
Select what kind of object this ACL secures. The type of object determines how the object is named and what operations are available. This field becomes read only after the ACL is created. If you want to change the type, you must delete the ACL and create one with the correct type. |
| Operation |
Select the operation that this ACL secures. Each object type has its own list of operations. An ACL can only secure one operation. To secure multiple operations, create a separate ACL for each.
If you’re creating an ACL for a report_view operation, see also Report_view access control.
|
| Decision Type |
Select the decision type of the ACL. Allow If allows access upon successful evaluation. Deny Unless denies access unless there’s successful evaluation. See Deny-Unless ACL for more information. |
| Admin overrides |
Select this check box to have users with the admin role automatically pass the permissions check for this ACL. Admin users pass regardless of what script or role restrictions apply. However, the nobody role, which only ServiceNow personnel can assign, takes precedence over the admin override option. If an ACL is assigned the nobody role, admin users can’t access the resource even when Admin overrides is selected. See Base system roles.
Clear this check box if administrators must meet the permissions defined in this ACL to gain access to the secured object. Since administrators always pass role checks (see the description of the Requires role field), use the condition builder or Script field to create a permissions check that administrators must pass.
|
| Protection Policy |
Select this to set the protection policy on the ACL. |
| Name |
Enter the name of the object being secured, either the record name or the table and field names. The more specific the name, the more specific the ACL. You can use the wildcard character asterisk (*) in place of a record, table, or field name to select all objects that match a record type, all tables, or all fields. You can’t combine a wildcard character and a text search. For example, inc* isn’t a valid ACL name, but incident.* and *.number are valid ACL names.
Note:
Select the blue triangle to manually enter the record name or the table and field names of the object being secured. Use this option to secure an object that doesn’t appear in the dropdown.
|
| Description |
Enter a description of the object or permissions that this ACL secures. |
| Applies To |
Select Add Filter Condition to create a filter for the table selected in the Name field. The ACL applies only to the records matching this filter condition. For example, you could create an ACL for the incident table that applies only to incidents with the Critical priority.
Note:
You must select a table in the Name field to use this option. ACLs beginning with * cannot use the Applies To filter.
|
| Active |
Select this check box to enforce this ACL. |
| Advanced |
Select this check box to display the Advanced Condition fields. See step 6. |
