Venny Permissions
Venny · Permissions
Govern the entire platform. Not just a few screens.
Venny can perform hundreds of actions across the programme. Its permissions model lets administrators govern those actions by role, responsibility, and operating context—without forcing every organisation into the same access structure.
Define
Start with clear roles
Use built-in roles for common responsibilities or create new roles around how your organisation actually operates.
Control
Set action-level access
Switch capabilities on or off with precision—from viewing data to approving, editing, triggering, and paying.
Govern
Keep authority bounded
AI can help configure access, but it cannot grant permissions beyond the authority of the person making the request.
Granular by design
Permissions that reach every action Venny can take.
Traditional roles usually govern a limited set of screens and predefined actions. Venny operates across the full programme, so its permissions must reach every capability available to a user or agent.
Administrators can combine those controls into roles that match real responsibilities—without relying on a small, hard-coded list that never quite fits.
⇄
Start with built-in roles. Create unlimited custom roles. Assign only the access each person needs, and route requests for greater authority to the right approver.
Built-in roles
Ready for common teams
Approver, compliance, finance, and other standard responsibilities provide a practical starting point.
Custom roles
Match your organisation
Create roles for programme leaders, regional teams, suppliers, interns, or any operating model you require.
Action-level
Control individual capabilities
Govern viewing, creating, editing, approving, exporting, triggering, and other platform actions separately.
Data scope
Limit what each role can see
Keep sensitive worker, supplier, contract, compliance, and financial information within the right boundaries.
AI-assisted
Describe the role you need
Ask Venny to propose a permission set, then review and approve it before assignment.
Guardrailed
Authority cannot be self-expanded
If a request exceeds the requester’s own access, Venny flags it and routes it for approval instead of applying it.
The access-control gap
A permission model should not stop at the menu.
Legacy SaaS permissions are usually tied to hard-coded pages and a small number of predefined roles. They struggle when an AI agent can search, reason, communicate, create, approve, and act across the entire platform.
Venny’s model governs the underlying actions themselves. That means the same level of control follows the user and the agent wherever work happens—not only when someone opens a particular screen.
Platform actions individually governable
∞
Custom roles and permission combinations
0
Unapproved authority escalations
Permissions in practice
Least access required for the job
Let an intern view selected programme records
custom role
Allow finance to review and approve invoices
finance
Give compliance control over policy decisions
compliance
Restrict suppliers to their own submissions
data scope
Escalate a request to trigger payment
approval
Compare
Control access at the level where work happens.
Traditional permissions
A small set of hard-coded roles
Permissions tied mainly to pages and menus
Broad access granted to make work possible
Custom roles require technical configuration
AI actions sit outside the access model
With Venny Permissions
Built-in and unlimited custom roles
Hundreds of actions governed individually
Data scope and action access configured separately
AI-assisted least-privilege role creation
Requests beyond authority routed for approval
FAQ