Roles for Dashboard Users
Walapay's dashboard supports role-based access control (RBAC) to help teams implement approval workflows and access controls. This guide explains the different user roles and their permissions.
Overview
Role-based access control allows you to assign specific permissions to team members based on their responsibilities. This is particularly useful for:
- Separation of duties: Different team members can create vs. approve payments
- Approval workflows: Require payments to be reviewed before processing
- Security: Limit access to sensitive operations
User Roles
Walapay supports four user roles with different permission levels:
Role | Create Payments | Approve Payments | Cancel Payments | Everything Else* |
---|---|---|---|---|
ADMIN | ✅ | ✅ | ✅ | ✅ Full access |
CREATOR | ✅ | ❌ | ❌ | ✅ Full access |
APPROVER | ❌ | ✅ | ✅ | ✅ Full access |
VIEWER | ❌ | ❌ | ❌ | ✅ Full access |
*"Everything Else" includes: viewing payments, managing customers, managing accounts, and viewing information
Role Descriptions
ADMIN
Full control over the platform
Admins have unrestricted access to all features. They can create, approve, and cancel payments, as well as manage team settings and user roles.
Best for: Team owners, finance managers, and administrators
CREATOR
Can initiate payments but cannot finalize them
Creators can create new payments, but these payments are placed in a "Pending Approval" state. An APPROVER or ADMIN must review and approve the payment before it's processed.
Best for: Team members who initiate payments but require oversight
APPROVER
Can review and approve payments but cannot create them
Approvers can review payments created by others and approve or cancel them. They cannot create new payments themselves.
Best for: Finance controllers, managers who review transactions
VIEWER
Read-only access to payments
Viewers can see all payment data but cannot create, approve, or cancel payments. They can still manage customers and accounts for their records.
Best for: Auditors, accountants, team members who need visibility without modification rights
Approval Workflow

When a CREATOR creates a payment, it enters an approval workflow:
- Creator initiates payment → Payment status:
PENDING_APPROVAL
- Approver reviews payment → Payment appears in "Awaiting Approval" section
- Approver approves or cancels → Payment status:
PENDING
(approved) orCANCELLED
- System processes payment → Only payments with
PENDING
status are processed
Payments created by CREATOR role appear in the "Awaiting Approval" section
Permission Enforcement
The dashboard will prevent users from accessing features they don't have permission for:

Users see helpful messages when they don't have permission for an action
API Keys
Note: API keys bypass role-based access controls and have full ADMIN privileges. This allows for programmatic integrations without role restrictions.
Sandbox Environment
In sandbox environments (for testing), role-based access controls are automatically disabled to allow unrestricted testing.
Getting Started
Please reach out to us to get started with RBAC for dashboard users. Full UI for role management coming soon
Updated 6 days ago