Venva allows vendors to control exactly what each team member can view, manage, and perform across the platform. Roles and permissions make it possible to delegate work across trades, offers, wallets, inventory, and operations without giving every user full access to your workspace.
This lets you build a team structure that matches how your operation actually runs.
What roles and permissions are used for
Inside Venva, roles and permissions help you:
control which parts of the platform a team member can access
decide what actions a team member can perform
separate visibility permissions from action permissions
protect sensitive operational and wallet functions
delegate work while keeping vendor-level oversight
This is especially useful when different team members handle different parts of your workflow.
Where roles are assigned and managed
Roles and permissions can be assigned during invitation and reviewed later from the Manage Roles view inside My Team.
This allows you to:
onboard users with the right access from the start
review their assigned permissions later
adjust access as their responsibilities change
Permissions can be assigned during onboarding based on the role the team member will have in your workspace.
The Manage Roles view lets you review and update a team member’s assigned permissions after they join.
General roles vs administrator roles
Venva separates permissions into two broad groups:
General Roles
These permissions control access to the main parts of the platform, such as:
Home
My Team
Trades
Offers
Inventory
P2P Wallets
Trade History
Trade Partners
Analytics
Team Activity
Swap
Automations
Tags
Marketcap
Currencies
These are the permissions most commonly used when assigning day-to-day operational access.
Administrator Roles
Administrator roles control more sensitive functions that affect your workspace at a higher level, such as:
Venva Wallet
Invite Team
Manage Team
Manage Payment Accounts
These permissions should only be given to trusted users.
Visibility permissions vs action permissions
Some permissions simply allow a team member to see an area of Venva. Others allow the team member to take action inside that area.
For example:
a user may have permission to access Trades, but separate permissions determine whether they can release, mark paid, cancel, dispute, or perform KYC on trades
a user may have permission to access Inventory, but separate permissions determine whether they can add, allocate, liquidate, assign, edit, or delete inventory
This separation gives vendors more precise control over what each team member can actually do.
Two-factor authentication requirements
For some permissions, Venva may require or strongly recommend two-factor authentication before a team member can be onboarded or granted access.
This is especially relevant for more sensitive permissions such as:
wallet-related permissions
invite / team-management permissions
other roles that affect funds, access, or delegation
This helps reduce risk when assigning higher-trust permissions inside your workspace.
Sensitive permissions may require two-factor authentication during onboarding for stronger account security.
How to assign permissions safely
A good way to assign permissions is to start with the minimum access a team member needs, then expand only where necessary.
A few practical examples:
give traders the trade permissions they need without also giving them wallet or team-management access
give inventory operators inventory permissions without automatically giving them administrative controls
reserve wallet, invitation, and team-management permissions for trusted users only
review role assignments regularly as responsibilities change
This keeps delegation efficient while reducing unnecessary risk.
Permissions can change over time
Roles and permissions are not fixed forever. As a team member takes on more responsibility, you can revise their access from the Manage Roles view.
This makes it easier to scale your operation without rebuilding your team structure from scratch each time someone’s responsibilities grow.
Why it matters
Venva’s permission system is designed to help vendors scale with control. Instead of giving every team member full access, you can decide exactly who can view, manage, or perform specific actions across the platform. This improves delegation, reduces operational risk, and makes accountability clearer across the workspace.