The right people see the right work.
Nobody else.
Your people sign in with the accounts they already use. What each person, partner and AI agent can see and do follows their role, and when someone leaves, their access goes with them.
Access usually breaks between systems
Each system you buy comes with its own users, its own passwords and its own idea of who can see what. The gaps show up later:
- A leaver is removed from email but still has access to two other systems.
- A partner is given a full account because there was no safe way to share one file.
- Approvals happen by email, so nobody can prove the approver was allowed to approve.
- An audit asks who could see customer records last quarter, and IT spends a week finding out.
When work moves through one platform, access is decided in one place, from your own directory.
Anubavam connects to your identity provider, such as Microsoft Entra ID, so people sign in with their existing accounts and multi-factor authentication. One permission model controls what staff, partners, customers and AI agents can see and do, down to record and field level. Every sign-in and permission change is recorded.
One identity, one set of rules, for everyone who touches the work
- Your sign-in, not oursPeople sign in through your identity provider, with your multi-factor rules and your conditional access policies. No new passwords to manage
- Access follows the rolePermissions are set by role, then narrowed by department, region, branch or customer. Sensitive fields can be hidden from roles that do not need them
- Outsiders, safely insidePartners, suppliers and customers get their own sign-in and see only their own requests and documents
- Leavers lose accessDisable someone in your directory and their access ends
- Approval rules enforcedA person cannot approve their own request. Cover during leave is time-limited and recorded
- AI agents treated like staffEach agent has its own identity, a named owner and permissions no wider than its job. See AI and Agents
Example: a supplier, a buyer and an approver
Illustrative. A supplier signs in through the supplier portal and uploads documents. They see their own application and nothing else. A buyer in procurement checks the documents; she can see suppliers for her region only, and bank details are hidden from her role. The approval goes to the category manager. If the buyer is also listed as the approver, the platform routes it to the next person. Every step, and every attempt to open a record outside a role, is recorded.
Illustrative
Proof of who could do what, and when
Knowing something is not the same as being allowed to act on it. The same permission rules apply to answers from Enterprise Knowledge and actions by AI agents.
- A record of access.Every sign-in, failed sign-in and permission change is recorded with who, when and from where.
- Administrators are controlled too.Administrator actions go through the same permission model and are recorded.
- Least privilege by default.New roles start with no access, and permissions are added on purpose.
- Ready for access reviews.Export who holds which role, for periodic sign-off by managers.
Works with the identity setup you already have
- You have: Microsoft Entra ID
- How it fits: Single sign-on and multi-factor authentication through Entra ID; your conditional access rules apply
- You have: Another identity provider using SAML 2.0 or OpenID Connect
- How it fits: Connected in the same way, confirmed during the technical consultation
- You have: Separate users outside your organisation
- How it fits: A separate sign-in for partners, suppliers and customers, kept apart from staff accounts
- You have: Strict network rules
- How it fits: Location, device and IP rules applied through your identity provider
See your own roles working on one process
In a technical consultation, your IT team walks through your identity setup with ours. In a Tailored Proof Session, we show your roles, your approval rules and your sign-in on one of your processes. The same identity model already runs for universities on Creatrix Campus, our higher education edition, built on the same platform.
Questions about identity and access.
Yes. Anubavam connects to your identity provider, such as Microsoft Entra ID, so staff sign in with their existing accounts and your multi-factor rules.
Yes, through your identity provider’s conditional access policies, which apply when people sign in.
When you disable them in your directory, their access ends. Their past actions stay in the record.
Yes. They get a separate sign-in and see only their own requests, documents and status.
Yes. Access can be limited by role, by record (such as region or branch) and by field.
Each agent has its own identity, a named owner and permissions limited to its job. Its actions are recorded like a person’s.
Yes. Sign-ins and permission changes are recorded, and you can export who held which role for an access review.