ANVE: the private AI office, on the record. See what that means
ANVEPrivate AI glossary · updated 2026-10-16
Short answer. Role-based access control (RBAC) gives people permissions through roles, such as partner, accountant or receptionist, instead of listing permissions person by person. NIST describes it as a model in which permitted actions on resources are identified with roles rather than individual identities: each user is assigned one or more roles, and each role carries one or more privileges. When someone joins, moves or leaves, you change their roles, not dozens of separate settings. For an AI system, roles decide who can query which document collections, who can approve an agent’s action, and who can read the activity log.
Users are assigned to roles, roles hold privileges, and privileges permit operations on resources. Security administration then means working out which operations people in a given job must perform and assigning employees to the proper roles. NIST’s project page says RBAC was formalised in 1992 by David Ferraiolo and Rick Kuhn, that NIST’s model was adopted as American National Standard 359-2004, and that it was revised as INCITS 359-2012. The project is now archived.
These roles are an example, not a description of any product.
| Role | Can | Cannot |
|---|---|---|
| Administrator | Manage users and roles, approve connectors and cloud models | Edit or delete the activity log |
| Auditor | Read the activity log and reports | Change settings or read private drafts |
| Team lead | Query the team’s documents, approve outputs for the team | Change roles or connectors |
| Staff | Use the apps and query documents they are allowed to see | See other teams’ documents |
| Guest or intern | Use one app on a limited collection | Export or share outside the office |
| Approach | How access is decided | Watch for |
|---|---|---|
| Per-person list (ACL) | A list of named people on each item | NIST: administrators specifying lists user by user find it costly and prone to error |
| RBAC | The roles a user holds | Too many roles; leavers and movers keeping old roles |
| Attribute-based (ABAC) | Rules over attributes such as department, device and time | NIST: can be easy to set up but complex to manage |
Roles must reach the AI’s search too. OWASP’s guidance on vector and embedding weaknesses warns that misaligned access controls can let a model retrieve and disclose content the person asking could not open directly, and recommends permission-aware stores. After setting up a document collection, test with two accounts: one in a role that may see a document, one that may not.
ANVE is built for many named users. Its security page (/security) says the roles today are administrator and user, and that teams, finer roles and single sign-on are not on ANVE yet. An administrator must approve cloud models, connectors and the tools an agent can use. Who can read whose chats is a question to settle in writing before a paid pilot.
No sealed ANVE unit exists; every image of the appliance on this site is a labelled render. The software runs today on a development machine. No customers yet, no certifications, no delivery date, and the final price is not announced.
Reservations are ₹999 in India or US$12 elsewhere, refundable in full until you confirm an order in writing (terms). Offices that cannot use cloud AI can apply to be one of ten design partners.