Support
ERP Access Help Center
Use this page when you need guidance on portal access, credential issuance, audit reviews, or operational escalation paths.
Portal access and sign-in
ERP Access is limited to active internal portal users. If sign-in fails, confirm that the account is active, uses the correct password, and still carries an allowed role (`admin` or `issuer`).
- Use `/portal/login` as the only guest entrypoint for internal operators.
- If login succeeds but a screen returns `403`, the account likely lacks that feature for its role.
- If the portal shows schema warnings to admins, run the migration command before relying on newer features.
Credential questions
Credential sets are issued from the portal and tied back to both a Volo account and a portal actor. Passwords and x-api-keys are one-time secrets, so the portal stores only safe masked hints for later review.
- Use `Regenerate secrets` if the actor has lost the API password or client x-api-key.
- Secret regeneration preserves the original expiry but revokes active gateway tokens tied to that credential set.
- Issuer users can only issue credentials for themselves; unrestricted credentials remain admin-only.
Operational review and escalation
Use the Logs and Audit pages before escalating a system issue. Those pages expose correlation IDs, policy decisions, matched endpoint rules, token history, request IPs, and safe request/response evidence.
- Start with `/portal/logs` for a narrow incident view and `/portal/audit` for a broader user-centered trail.
- Capture the correlation ID from the client-facing response whenever possible.
- If relay access fails, verify upstream configuration under the relevant Volo account before assuming the gateway is at fault.