acl-security

Create and configure record and field-level ACLs in ServiceNow.

77|23|Updated Jul 16, 2025
One-click install
npx skills add https://github.com/groeimetai/snow-flow --skill acl-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acl-security
Source: https://github.com/groeimetai/snow-flow/tree/main/packages/opencode/src/bundled-skills/acl-security
Command: npx skills add https://github.com/groeimetai/snow-flow --skill acl-security

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps manage and configure Access Control Lists (ACLs) in ServiceNow to enforce granular security rules for data access.

Core Features & Use Cases

  • ACL Creation: Define record and field-level ACLs with roles, conditions, and scripts.
  • Security Auditing: Understand ACL evaluation order and common security patterns.
  • Use Case: You need to ensure that only users with the 'itil' role can read 'incident' records that are currently active. This skill can help you create the appropriate ACL.

Quick Start

Use the acl-security skill to create a read ACL for the incident table that requires the 'itil' role.

Frequently Asked Questions about acl-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure ServiceNow ACLs to restrict record access based on roles?

ServiceNow ACLs restrict record access by defining role-based security rules. You can configure read, write, create, or delete operations by assigning specific roles like 'itil' to the Access Control List for a table such as incident.

What is the evaluation order of Access Control Lists in ServiceNow?

Access Control Lists in ServiceNow evaluate from table-level down to field-level rules. Understanding this evaluation order helps apply common security patterns and ensures robust data protection by enforcing the most restrictive requirements correctly.

Can I use scripts and conditional logic in ServiceNow field-level security rules?

ServiceNow field-level security rules support script-driven enforcement and conditional logic. You can create ACLs with custom scripts that evaluate runtime conditions alongside role requirements to granularly control access to specific fields.

What is the best way to secure active incident records so only itil roles can read them?

Securing active incident records requires creating a read ACL on the incident table. You enforce this by requiring the 'itil' role and adding a conditional check for active records, ensuring only authorized users view them.

When should I use script-driven enforcement instead of role-based ACLs in ServiceNow?

Use script-driven enforcement in ServiceNow ACLs when role-based access alone is insufficient. Scripts allow you to evaluate complex runtime conditions, such as checking record state or user assignments, to implement advanced security patterns.