Skip to main content
Aiviance docs

Data & AI

Accounts, roles and access controls

How identity, entity scope, roles, step-up authentication and advisor consent limit access to financial information.

Reviewed October 24, 2026Data & AI2 min read
Open

Access in Aiviance is not determined by whether someone can see a link. Authentication, current membership, entity scope and operation-level policy are checked on the server.

Every request starts with an identity and scope

A signed-in user operates inside an active personal, family or business context. Requests resolve the entities that identity may access; an entity identifier used by the interface is not, by itself, authority to read or change that entity.

The product interface can hide unavailable actions for clarity, but interface visibility is not treated as a security control.

Roles limit what can happen inside the scope

Business access is derived from current tenant membership, active entity grants and the user's role. Family and personal access use their own subject-scoped permission paths. Module entitlements and finance-write controls apply in addition to those roles.

For agent actions, current business authority is resolved again before every tool runs. This prevents an old conversation from retaining authority after a person is removed or an entity grant is revoked.

Sensitive operations require stronger proof

Selected operations require a fresh step-up authentication for that exact action. Examples include creating or removing a bank connection, changing a TFN, transferring tenant ownership, disabling an MFA factor, starting account deletion, updating a payout method and executing a payment run.

An AI conversation cannot route around that requirement. The agent path checks the same sensitive-operation registry as the corresponding product route.

Advisors act through explicit authority

Advisor access is not implied by belonging to an accounting or advisory practice. It depends on the relevant client consent and entity permission. Removing that authority should remove the advisor's ability to act on behalf of the client.

Access is recorded

Security-relevant authentication, authorisation, privilege and financial events are written to the platform audit trail with the actor, time, action and request context. Operational logs and the audit trail have different purposes and retention periods.

Customers should assign individual accounts, avoid shared credentials, review memberships and entity grants regularly, and remove access promptly when responsibilities change.