From the ServiceNow edition of November 5, 2026
Introducing the Access Analysis Agent: Your Quick Answer to "Can This User Access This?"
ServiceNow (Community article by ServiceNow employee) · Enterprise platform security/administration; applies to ServiceNow customers including public sector · Global
- Publisher
- ServiceNow Community (ServiceNow AI Platform blog)
- Original publication
- 2026-11-05 (posted ~7 hours before retrieval)
- Source retrieved
- 2026-11-06
- Event date
- 2026-11-05
What happened
In the Brazil release, ServiceNow introduced an Access Analysis Agent in the ServiceNow Otto panel that answers natural-language questions about whether a user, group, or role can access tables, records, AI agents, or agentic workflows. Results are Passed, Blocked, or Undefined, naming the blocking ACL, role, security attribute, or condition, and flagging scripts that need manual review. Results are logged in Access Analyzer. Available to admins/security with access_analyzer_admin or user_admin. Corroborated in Access Analyzer Brazil release notes and the ServiceNow Store listing (Paid; Compatibility: Brazil; scope sn_acl_ai_agents).
Why it matters
Directly relevant to state/local, university and K-12 ServiceNow platform teams that must evidence least-privilege access for AI agents and agentic workflows under audit. Conversational ACL investigation can shorten access reviews during Brazil upgrades. No government customer is cited; effectiveness and accuracy are unvalidated outside vendor materials.
Evidence and measured results
Vendor-employee community post dated 2026-11-05; corroborating Access Analyzer release notes and Store app page inspected. No independent evaluation, accuracy rates, or public-sector deployment evidence.
Limitations and uncertainty
Vendor claim only; Paid Store app; accuracy of conversational ACL answers not independently measured; no SLED deployment cited.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-06; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Platform and security teams struggle to evidence who can access AI agents and sensitive tables during audits and Brazil upgrades.
- Stakeholders
- ServiceNow platform owner
- CISO
- Internal audit
- Identity/IAM lead
- Discovery questions
- Are you on or planning Brazil?
- Do you already license Access Analyzer and the Access Analysis AI Agents Store app?
- How do you today prove access to AI agents and agentic workflows?
- Who holds access_analyzer_admin or user_admin?
- Value hypothesis
- If ACL investigations dominate upgrade and audit cycles, a conversational Access Analyzer front-end may shorten discovery time; magnitude unproven in SLED.
- Potential engagement
- A bounded access-review readiness assessment tied to Brazil upgrade planning.
- Unsupported claims
- The agent is independently accurate on all ACL types
- It remediates recent ServiceNow AI Platform CVEs
- It is included at no extra cost for all customers
Pre-sales engineering
Role takeaway
- Fit
- Fits Brazil instances with Access Analyzer and entitlement to Access Analysis AI Agents.
- Architecture and integration
- Otto/Now Assist panel agent calling Access Analyzer; evaluates tables, records, fields, Script Includes, UI pages, AI agents, agentic workflows.
- Prerequisites
- Brazil release
- Access Analyzer
- access_analyzer_admin or user_admin
- Store app entitlement if required
- Constraints
- Paid Store listing
- Scripted ACLs may need manual review
- No independent accuracy data
- Security
- Limit who can run evaluations; treat results as sensitive configuration intelligence; do not substitute for CVE patching.
- Proof of value
- Agreement rate vs known ACL fixtures
- Evaluations logged in Access Analyzer
- Correct identification of blocking ACL on AI agent resources
Delivery
Role takeaway
- Work
- Pilot conversational access questions against a fixture set during Brazil upgrade; document gaps on scripted ACLs.
- Dependencies
- Brazil upgrade window
- Security reviewers
- Store/licensing confirmation
- Ownership
- Platform team with security sign-off.
- Skills and adoption
- Train admins on question patterns and when to fall back to Access Analyzer/Simulator.
- Governance checkpoints
- Role assignment review
- Evaluation-log retention
- Change process for ACL fixes
- Acceptance criteria
- Proposed: >=95% agreement with known fixtures
- Proposed: AI-agent resource checks included in the fixture pack
- Risks
- False confidence on scripted ACLs
- Unlicensed Store app
- Over-broad admin role assignment
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Agent sits on Access Analyzer engine inside the Otto/Now Assist panel; can use current page context and evaluate access to AI agents and agentic workflows as resources. Store app scope sn_acl_ai_agents; Paid; Brazil-compatible.
Governance
Who approves, reviews and stays accountable for outcomes?
Supports audit and recertification workflows by logging evaluations in Access Analyzer, but does not itself change ACLs. Agencies still need policy on who may run evaluations and how results feed access reviews.
Security and privacy
What data, permissions and controls need testing?
Helps find over-permissioned or blocked access including on AI agents; does not remediate October AI Platform CVEs. Role gating (access_analyzer_admin/user_admin) matters because the agent reveals ACL and condition details.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Reduces manual ACL digging for platform admins; still requires security skill to act on results and review scripted ACLs the agent flags.
Procurement
What should contracts, pricing and exit terms secure?
Store lists the Access Analysis AI Agents app as Paid and Brazil-compatible; confirm entitlement and licensing before assuming it ships with base Access Analyzer.
Operating model
Which teams own the service once it runs?
Access troubleshooting and AI-agent permission reviews become conversational tasks for designated admins, with Access Analyzer as the system of record for evaluation logs.
Publication history
- 2026-11-05ServiceNow · Issue 063 resources
Stable resource ID: servicenow-access-analysis-agent-brazil-20261105