AI Agent ERP Access Request Form Template
When an AI agent gets an ERP login, it is a new privileged identity, and most companies approve it by chat message. This form turns that request into a signed record of what the account can reach, how often and until when.
Fill in
AI Agent ERP Access Request Form Template
AI Agent ERP Access Request
Company: Acme Precision Ltd Requested by: J. Rivera, Integration Developer Date: 2026-10-20 Agent: purchasing-assistant-mcp System: Infor SyteLine, TEST company
Business purpose
Answer buyer questions about open orders and late deliveries without opening multiple screens.
Account and access
Service account: svc_ai_purchasing Access level: Read only Objects needed: Purchase orders, PO lines, vendors, item master, on-hand balances Limits: Max 200 rows per call, 30 calls per minute Review or expiry: 2027-04-20
Controls confirmed
| Control | Confirmed (Y/N) | Notes |
|---|---|---|
| Account is non-interactive and not shared with a person | ||
| Role limited to the objects listed above | ||
| Every call logged with user prompt and query | ||
| Write actions require human approval | ||
| Credentials stored in a secrets manager | ||
| Account disabled when the request expires |
Approvals
This is a starting point for your internal process, not legal or compliance advice. Align the role names and environments with your own ERP and change management policy.
Scope an agent role for my ERP
Optionally ask for help mapping this request to real roles in your ERP.
Optional. The tool and every export work without this. No spam.
How to use the form
Fill in the agent name, the ERP and environment, the service account and the objects it needs. Be specific in the objects field: write purchase orders and vendors, not purchasing. Choose the lowest access level that serves the stated purpose, then set row and rate limits and an expiry date. Export to PDF or Word, route it for the four signatures and attach it to your change ticket. Request test and production access in separate forms.
Why least privilege matters more for agents
A human user opens a screen and sees what the screen shows. An agent can chain tool calls, loop over thousands of records and combine data the person never saw together. That is why the form asks for limits and a review date, not just a role. Model errors are rarely malicious; they are confident mistakes, and a narrow role keeps the mistake small. Where the ERP supports it, use a dedicated role or security group rather than copying an existing power user.
- One service account per agent or server
- No shared credentials with a human
- Separate accounts for read and write paths
Example walkthrough
The sample request is a purchasing assistant with read-only access to purchase orders, vendors, items and on-hand balances, capped at 200 rows per call. That is enough to answer which orders are late and which vendor to chase. If the team later wants the agent to propose date changes, they raise a new request at the Read and update with approval level, and the approvers see the change in scope immediately.
Common mistakes
The usual failures are an open-ended expiry, reusing an integration user that already has broad rights, and skipping the logging control because the ERP's native audit does not capture the agent's prompt. Log the model prompt and the generated query on your side as well, so an auditor can connect a business question to a database read.
Frequently Asked Questions
Should an AI agent use a named user account?
Prefer a dedicated non-interactive service account per agent. It keeps activity separable from human users, can be disabled in one step and makes audit review simpler. Avoid reusing an employee login or a general integration user.
What expiry period is reasonable?
Many teams use three to twelve months for service accounts, then re-approve. Short periods suit pilots. The key is that the date exists and someone owns the renewal.
Does this replace my change management process?
No. It supports it. Attach the exported form to your existing ticket so approvers see scope, limits and controls in one place, and adapt the control list to your own policy.
What if the agent only reads data?
You still need the form. Read access can expose pricing, payroll or customer data. Record the objects, row limits and logging so the exposure is deliberate and reviewable.
Netray deploys ERP agents that are read-only by default, show the query and respect ERP roles. If you want help scoping the right role for your system, get in touch.
Related Tools
MCP Tool Catalog and Risk Worksheet
Register each MCP tool your agent exposes, the ERP object it touches and a computed risk score, then export to Excel.
Compliance & ContractsAgent Action Audit Log Worksheet
Record agent actions, the tool called, the ERP record affected and the approver, with a computed latency and exception count.
Compliance & ContractsAI Agent Incident Response Runbook Template
A fill-in incident report for AI agent mistakes in the ERP: timeline, containment, root cause, data affected and corrective actions.
Developer ToolsMCP Server Deployment Runbook Template
A fill-in runbook covering host, secrets, network, health checks, monitoring and rollback for an MCP server in front of an ERP.
More Developer Tools tools
See all- SAP Sales Order ABAP SELECT Generator (VBAK, VBAP, VBFA)
- SAP Sales Order Create BAPI ABAP Generator (BAPI_SALESORDER_CREATEFROMDAT2)
- SAP ABAP Open Items SELECT Generator
- SAP ACDOCA SQL Query Generator
- SAP QM Inspection Lot ABAP SELECT Generator
- SAP Quality Notification Pareto SQL Query Generator
- SAP QM Usage Decision BAPI Skeleton
- ABAP Custom Exception Class Generator
- ABAP Unit Test Class Generator