Granting Audit Access — Acumatica
Time required: 5 minutes Who should do this: Anyone with Acumatica admin access What we get: Read-only API access to check schema health, customization risk, and upgrade readiness What we can't do: Create, modify, or delete any data
Step 1: Create the API user
- Open SM201010 (Users)
- Click + to add a new user
- Fill in:
- Login:
studio-b-audit - Password: (generate a strong password — you'll share it with us securely)
- Email: your admin's email (for password reset if needed)
- Login:
- Save
Step 2: Assign the read-only role
- On the same user record, scroll to Roles
- Add the role: API User (or your equivalent read-only role)
- If you don't have a read-only role, assign these minimum roles:
BI(Business Intelligence — read-only to most entities)- If
BIisn't available, any role that grants read access to: Sales Orders, Customers, Stock Items, Purchase Orders, Invoices, Shipments
- Do NOT assign: Administrator, Full Access, or any role with write/delete permissions
- Save
Step 3: Verify the API endpoint
Confirm your Acumatica instance URL. It will look like one of these:
https://yourcompany.acumatica.comhttps://erp.yourcompany.com
We need the base URL — not a screen URL.
Step 4: Send us the credentials
Share these three things with your Studio B contact:
- Acumatica URL (e.g.,
https://yourcompany.acumatica.com) - Username:
studio-b-audit - Password: (use a secure method — we accept encrypted email, 1Password share link, or verbal over a call)
Tenant name (if multi-tenant): find this on the login screen dropdown.
What we check
| Check | What it tells you |
|---|---|
| Entity schema health | Are your customization fields properly defined? |
| Customization risk score | How complex are your customizations? Will they survive an upgrade? |
| API configuration | Is your REST API properly configured and accessible? |
| Custom field inventory | What custom fields exist and are they consistent? |
| Sub-entity availability | Are related records (contacts, addresses, line items) accessible? |
After the audit
We'll revoke our own access by asking you to disable the studio-b-audit user. Or you can disable it yourself in SM201010 at any time — the audit takes about 15 minutes to run, so the user only needs to be active for that window.