Read tools
Authorised business data can be searched, filtered and summarised.
- Customers and projects
- Tasks and deadlines
- Time and utilisation
- Documents and metrics
Integration · ChatGPT and MCP
Work in the preferred chat. Retain ERP controls.
An authenticated MCP connection exposes selected ERP tools. The agent can only read data or propose actions allowed by tenant, role and approval policy.
The problem
A convenient chat must not remove ERP control boundaries.
Authentication, tool scope, data visibility and confirmations are enforced server-side. A prompt never decides permissions by itself.
Write tools
Allowed actions are validated and can require confirmation before execution.
- Create task
- Record time
- Create customer or project
- Draft instead of irreversible action
Security model
The connection carries the same organisational boundaries as the ERP.
- MCP authentication
- Tenant binding
- Role check per tool
- Revocation and audit
Agent flow
Convenience outside, control inside.
- 01
Connect
Authenticate a supported client securely.
- 02
Ask
Agent selects an allowed ERP tool.
- 03
Check
Server validates role and input.
- 04
Confirm
Approve critical actions deliberately.
FAQ
ChatGPT integration questions
Is all ERP data sent to the model?
No. Only data needed and authorised for the concrete tool response should be transferred. The exact flow depends on the client and model provider.
Can a prompt bypass permissions?
No. Permissions are enforced server-side in the ERP and must not depend on chat wording.
Can access be read-only?
Yes. The tool catalogue can be restricted to queries only.
More about agents
Next step
Which chat should solve which ERP task?
We review client, data flow, roles, tools and confirmation duties.