Security and permissions

Who can do what in ERPoida, and how the AI assistant stays inside the same rules as everyone else.

7 stepsFor admins and finance leads

  1. Roles decide who can do what

    A role is a named set of permissions, each one an action in an app, such as viewing or changing invoices. Admins assign roles to people under Users & Roles.

  2. Two checks on every request

    Every request passes two checks: is the app switched on for your organization, and does your role allow the action. Both apply the same way whether you click, call the API or ask the assistant.

  3. The assistant acts as you

    The AI assistant works with the permissions of the person using it. It cannot see an app that is switched off or do anything that person’s role does not allow.

    Automations follow the same rule: every step runs with the permissions of the flow’s owner, so a flow can never do something its owner could not do by hand.

  4. Every action is recorded

    Tool calls made by the assistant, including those from Claude or ChatGPT, are recorded in the action log with their inputs and outcome. Records keep their history, so you can see what changed and when.

  5. Accounting cannot be rewritten quietly

    Entries always balance, a closed fiscal period refuses new entries, and a price that has been used on a posted invoice is locked. These rules are enforced by the database itself, not only by the screen.

  6. Access tokens and connected assistants

    Access tokens, including the ones Claude or ChatGPT receive when you connect them, are listed in Settings → Access tokens. Revoke one there and that access stops.

    How to connect Claude or ChatGPT →

  7. Where your data is processed

    The built-in assistant uses AI models through AWS Bedrock in the European Union (Frankfurt region). Card details are entered only on pages hosted by Stripe.

    Read the privacy notice →

Next steps

← All guides