Venny Permissions
VENNY PERMISSIONS
Authority stays bounded, even when work moves fast.
Venny can prepare work, route tasks, trigger actions, and support decisions across the program. Permissions keep each person and agent within the right role, data scope, approval boundary, and operating context.
01 · DEFINE
Design roles around real responsibility.
Start with common roles, then create custom access for program leaders, regional teams, suppliers, finance, compliance, and temporary support.
02 · CONTROL
Govern what can actually be done.
Control who can view, create, edit, export, approve, trigger, escalate, or release work — without handing out broad access just to keep things moving.
03 · ROUTE
Anything beyond authority is routed to the right approver.
Venny can suggest access, but it cannot grant authority beyond the requester’s own permission. Anything higher is routed for approval.
LEAST-PRIVILEGE ACCESS
AI-native work needs AI-native permissions.
Venny governs the actions that move work: reviewing evidence, changing status, requesting documents, approving invoices, routing exceptions, and triggering payments.
Administrators can combine action-level controls, data scope, approval boundaries, and AI-assisted recommendations into roles that match how the program actually operates.
⇄
Least-privilege by default: each person gets the minimum access needed for the job, and anything above that is routed for review.
01 · Built-in roles
Start from common responsibility sets
Approver, compliance, finance, supplier, and program roles give administrators a practical starting point.
02 · CUSTOM ROLES
Match how your organization works
Create roles for regional operators, supplier teams, legal reviewers, finance approvers, interns, executives, or temporary support.
03 · ACTION-LEVEL CONTROL
Control what can actually be done
Govern viewing, creating, editing, approving, exporting, triggering, escalating, releasing, and other platform actions separately.
04 · DATA SCOPE
Limit what each role can see
Keep worker, supplier, contract, rate, compliance, and payment information visible only to the right people.
05 · AI-ASSISTED SETUP
Describe the role you need
Ask Venny to propose a permission set, then review the suggested access before it is assigned.
06 · GUARDRAILED AUTHORITY
Authority cannot expand itself
If a request exceeds the requester’s authority, Venny flags the conflict and routes it for review instead of applying it.
THE ACCESS CONTROL GAP
Legacy permissions stop at the page. Venny works at the action.
Traditional SaaS permissions control menus, modules, and pages. But AI-native work needs deeper control: who can see which data, which actions can be prepared, which decisions need approval, and where exceptions should route.
That is why permissions must govern the underlying action itself. The same boundary follows the user and the agent wherever the work moves.
Controls screens, modules, and menus.
Action control
Governs what users and agents can actually do.
Data scope
Separates what users can see from what they can do.
Approval route
Routes anything beyond authority to the right approver.
PERMISSIONS IN PRACTICE
Least access required for the job
Let an intern update onboarding statuses without seeing rates
custom role
Allow finance to review invoices and release payment exceptions
finance
Give compliance control over classification and evidence rules
compliance
Restrict suppliers to their own submissions, rates, and candidates
data scope
Route a payment trigger request to the right approver
approval
HOW PERMISSIONS COMPARE
Access should be governed where the work happens.
Traditional permissions
Access is tied mainly to roles, pages, and menus
Broad permissions are granted to make work possible
Data scope and action authority are often bundled together
Custom access requires admin work or technical configuration
AI actions are not governed at the action level
With Venny Permissions
Access is shaped around responsibility and context
Each action can be governed separately
Data scope and action authority stay separate
Venny can propose least-privilege roles for review
Requests beyond authority are routed to the right approver
FAQ