[ SOX / Access reviews ]

Quarterly access reviews, prepared by read-only agents

engini lets an agent with read-only tools pull users, roles and permissions from NetSuite, SAP S/4HANA, Salesforce and Workday, compare them with your HR data and your segregation-of-duties rules, and prepare the review package for each owner. The agent cannot change access, because it was never given a tool that can. Every extract is recorded.

NetSuiteSAP S/4HANASalesforceWorkdayGoogle Sheets
Read about engini skills →
Quarter-end access review
  1. Quarter end, 6:00schedule trigger
  2. NetSuite logo
    Users and roles readNetSuite, SAP, Salesforce: read-only toolset
  3. HR data readWorkday: active workers and managers
  4. Compared with your rulesleavers with access; SOD conflicts
  5. Review sheets preparedone per owner, with findings first
Illustration of the flow on this page, not a product screen.
What it is
Review packages and SOD findings prepared by a read-only agent
Control area
ITGC: access to programs and data; periodic access review
engini provides
Read-only toolsets, connections to each system, recorded extracts
You still own
The SOD ruleset, the reviewer’s sign-off, the access changes
[ 01 / The problem ]

Access reviews are a spreadsheet project every quarter

Periodic user access reviews are a standard control over financial systems, usually quarterly for in-scope applications. The work is the same every time: extract users and roles from NetSuite, SAP and Salesforce, match them to HR records, email spreadsheets to managers, chase sign-offs, then prove removals happened. Auditors add a harder question: is the listing complete and accurate? PCAOB inspectors have flagged audit teams that did not test controls over the accuracy of user access listings (PCAOB, 2024).

Segregation of duties sits on top. The same individual able to prepare and post journal entries is one of the most frequent findings in the PCAOB’s inspection reports (PCAOB, 2025), and conflicts across systems are hard to see from inside any one of them.

Where the quarter goes

  • Extracting users, roles and permissions system by system.
  • Matching accounts to people, and finding leavers who still have access.
  • Checking role combinations against the SOD matrix by hand.
  • Integration and service accounts left out of the review.

A read-only agent does the preparation

With engini, an agent gets a toolset of read tools only: users, roles and permissions from NetSuite, SAP S/4HANA and Salesforce, and workers and managers from Workday or your HR data. It cannot change access, because it has no write tools, and engini refuses any call outside the toolset. It compares the access with HR status and with the SOD rules you define, and writes one review sheet per owner, with leavers and conflicts at the top.

Every extract runs through engini and is recorded under the person who ran it, so you can show how the listing was produced. The review itself, the sign-off and the access changes stay with your people and your normal provisioning. engini is not an identity governance product: it has no certification campaigns, no SCIM and no built-in SOD library.

[ 02 / How it works ]

Extract, compare, prepare, then people review

01 / Scope

A read-only toolset

Build a toolset with read tools only, on connections whose ERP roles can read users and roles but change nothing.

02 / Extract

Every system, recorded

A scheduled run reads users, roles and permissions from each system and workers from HR, each call recorded under the person who ran it.

03 / Compare

HR and SOD rules

The agent flags leavers and movers with access, and role combinations that break the SOD rules you defined, including service accounts.

04 / Prepare

Packages for owners

It writes one review sheet per owner. Owners review and sign off in your process; access changes go through normal provisioning.

[ 03 / What the agent reads and writes ]

What the agent reads, and only reads

SystemRecordsAccess
NetSuiteEmployees, roles and permissionsRead
SAP S/4HANAUsers and role assignments exposed through your OData servicesRead
SalesforceUsers, profiles, permission setsRead
Workday or your HR dataWorkers, status, managersRead
Google Sheets or ExcelReview packages for each ownerWrite
[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the word review under the line "Prepared by a read-only agent", and three labels: leavers, SOD conflicts, owner sign-off

Editorial image: the exceptions, found first.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account using my read-only connections: on the last day of each quarter, read active users and their roles from NetSuite and Salesforce, read active workers from Workday, list any NetSuite or Salesforce user who is not an active worker, and write the list to a new tab in the "Access review" Google Sheet. Do not change anything in any system.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

Read only by design, reviewed by people

Enforced

No write tools

The agent’s toolset contains read tools only, enforced on the server for CLI, SDK and REST API calls. The ERP roles on its connections are read only too.

Recorded

Extracts on the record

Every extract runs through engini and is recorded under the person who ran it, with the audit log available for export.

Yours

Rules and sign-off

You define the SOD ruleset and the review steps. Owners sign off in your process, outside the agent run.

Not offered

Not an IGA tool

engini has no certification campaigns, no SCIM provisioning and no built-in SOD library, and agent output must be checked before you rely on it.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect your systems, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can an AI agent automate our SOX user access review?

It can automate the preparation: extracting users and roles, matching them to HR data, flagging leavers and SOD conflicts, and writing the review packages. The review and sign-off stay with your owners.

How do we know the agent cannot change access?

Its toolset contains read tools only, and engini refuses any call outside it. Use connections whose ERP roles are read only as well, so both layers prevent changes.

Which systems can it read?

NetSuite, SAP S/4HANA (through the OData services you expose), Salesforce and Workday, plus databases and files. What it can read depends on the role behind each connection.

Will auditors accept the extract?

That is your auditor’s decision. engini records each extract under the person who ran it, which helps you document how the listing was produced and show it is complete.

Does this replace our identity governance tool?

No. engini is not an IGA or GRC product. It prepares the evidence and findings; certification campaigns and provisioning stay in your existing tools and processes.