ERP.AI
Access that follows the person and the task.
Keep organization identity, application access, and business decisions explicit as more people and software join the work.
Begin with a named caller.
ERP.AI separates organization and user identity from app permissions. The identity service handles users, service accounts, keys, and supported directory connections. The Permission API owns roles, permissions, assignments, and invitations.
For an integration or agent, choose credentials and assigned access suited to its work. An employee’s ability to perform a task does not mean every connected client should inherit the same access.
Review the controls in the context of your app.
Organization boundary
Confirm the organization and app the caller is working in, especially where a user belongs to more than one organization.
Role and resource access
Test both the allowed operation and an operation outside the role. Review access as roles and business responsibilities change.
Human approval
Use a named review step for sensitive business actions. Access to submit a request and authority to approve it are separate decisions.
Evidence
Review the action, change, and execution records available from the owning service, including the retention and export requirements for your deployment.
Make security evaluation specific.
Bring your identity requirements, data classification, deployment constraints, audit needs, and incident-response expectations to an enterprise review. Certification coverage, encryption options, residency, service commitments, and support terms depend on the contracted deployment and applicable documentation.
For a suspected vulnerability, use the published security contact. Include a clear description and reproduction steps without sending passwords, API keys, or unnecessary customer data.
Put ERP.AI to work for your business.
Choose an application, then configure the records, roles and workflows your team needs.