Skip to main content
Paymenter uses a role-based access control (RBAC) system to manage user permissions. This allows you to create custom roles with specific permissions and assign them to users.

​
User Management

Access user management at Admin Panel → Administration → Users or visit /admin/users.

User Accounts

Create, edit, and manage customer accounts

Role Assignment

Assign roles to grant admin permissions

Account Details

View services, invoices, credits, and tickets

Search & Filter

Find users by name, email, role, or service status

​
User List

The user list displays all registered users with:
  • First Name & Last Name - User’s full name
  • Email - Primary email address (searchable)
  • Role - Assigned role (if any)
  • Credits - Account credit balances (if user has credits)
  • Created At - Registration date
Source: app/Admin/Resources/UserResource.php:86

​
Searching Users

Available filters:
  • Role - Filter by assigned role
  • Email Verified - Filter users who have verified their email
  • Has Active Services - Show only users with active services

​
Creating Users

1

Navigate to Users

Go to Admin → Administration → Users and click New User
2

Enter User Information

Fill in the required fields:
  • First Name (required)
  • Last Name (required)
  • Email (required, must be unique)
  • Password (required)
3

Assign Role (Optional)

Select a role from the dropdown to grant admin permissionsLeave blank for regular customer accounts
4

Create Account

Click Create to save the new user
Passwords are automatically hashed using Laravel’s secure password hashing. They cannot be retrieved in plain text.
Source: app/Admin/Resources/UserResource.php:51

​
Editing Users

Click any user in the list to access the edit interface.

​
Basic Information

  • Edit first name, last name, and email address
  • Email must remain unique across all users
  • Changes are audited (tracked in audit log)
  • Enter a new password to change user’s password
  • Field is optional (leave blank to keep existing password)
  • New password is hashed on save
  • Change user’s role via dropdown
  • Searchable and preloaded for quick selection
  • Remove role to revoke admin access

​
Security Settings

Field: tfa_secretToggle to disable a user’s 2FA if they’ve lost access to their device.
  • Only visible if user has 2FA enabled
  • Toggle off to remove 2FA requirement
  • User must re-enable 2FA from their account
Field: email_verified_atManually verify a user’s email address.
  • Toggle on to mark email as verified
  • Sets verification timestamp automatically
  • Useful for manually created accounts
Source: app/Admin/Resources/UserResource.php:64

​
User Sub-Navigation

When editing a user, access additional pages via tabs:

Services

View all services owned by the user

Invoices

Access user’s invoice history

Credits

View and manage account credits

Tickets

See all support tickets from user

Billing Agreements

Manage recurring payment agreements

Properties

Custom user properties and metadata
Source: app/Admin/Resources/UserResource.php:145

​
Role Management

Access role management at Admin Panel → Configuration → Roles or visit /admin/roles.

​
Understanding Roles

Roles are collections of permissions that control access to admin panel features.
Paymenter includes a default “Admin” role (ID: 1) with full permissions. This role cannot be edited or deleted.

​
Role List

Displays all roles with:
  • Name - Role display name
  • Permissions - Count of assigned permissions (or “All” if wildcard permission)
Source: app/Admin/Resources/RoleResource.php:54

​
Creating Roles

1

Create New Role

Navigate to Roles and click New Role
2

Name the Role

Enter a descriptive name (e.g., “Support Manager”, “Billing Staff”)
  • Must be unique
  • Maximum 255 characters
3

Select Permissions

Choose permissions from the checkbox list:
  • Organized by feature area
  • Use bulk toggle to enable/disable all in a category
  • Use search to find specific permissions
4

Save Role

Click Create to save the role
Source: app/Admin/Resources/RoleResource.php:30

​
Permission System

​
Permission Structure

Permissions follow a hierarchical naming convention: 
admin.<resource>.<action>
Examples:
  • admin.users.view - View user list
  • admin.users.create - Create new users
  • admin.users.update - Edit existing users
  • admin.users.delete - Delete users
  • admin.settings.view - View settings
  • admin.settings.update - Modify settings

​
Core Permissions

  • admin.users.view - Access user list
  • admin.users.create - Create users
  • admin.users.update - Edit users
  • admin.users.delete - Delete users
  • admin.roles.view - Access role list
  • admin.roles.create - Create roles
  • admin.roles.update - Edit roles
  • admin.roles.delete - Delete roles
  • admin.settings.view - View settings page
  • admin.settings.update - Modify system settings
  • admin.widgets.overview - View overview statistics
  • admin.widgets.revenue - View revenue chart
  • admin.widgets.active_users - View active users
  • admin.widgets.support - View support tickets widget
  • admin.products.view - View products
  • admin.products.create - Create products
  • admin.products.update - Edit products
  • admin.products.delete - Delete products
  • admin.services.view - View services
  • admin.services.update - Manage services
  • admin.invoices.view - View invoices
  • admin.invoices.create - Create invoices
  • admin.invoices.update - Edit invoices
  • admin.transactions.view - View transactions
  • admin.tickets.view - View tickets
  • admin.tickets.create - Create tickets
  • admin.tickets.update - Respond to tickets
  • admin.tickets.delete - Delete tickets
  • admin.categories.view - View product categories
  • admin.categories.create - Create categories
  • admin.categories.update - Edit categories
  • admin.categories.delete - Delete categories
  • admin.tax-rates.view - View tax rates
  • admin.tax-rates.create - Create tax rates
  • admin.tax-rates.update - Edit tax rates
  • admin.tax-rates.delete - Delete tax rates

​
Wildcard Permission

The wildcard permission * grants full access to all admin features. Only assign this to trusted administrators.
When a role has the * permission, permission checks always return true. Source: app/Admin/Resources/RoleResource.php:60

​
Extension Permissions

Extensions can register additional permissions: 
Event::dispatch('permissions', [...])  // Extensions add permissions here
Custom extension permissions appear in the role editor alongside core permissions. Source: app/Admin/Resources/RoleResource.php:32

​
Permission Checking

Permissions are checked using the hasPermission() method: 
auth()->user()->hasPermission('admin.users.view')
Resources use this in:
  • canAccess() - Control page access
  • canView() - Control list view
  • canCreate() - Control record creation
  • canEdit() - Control record editing
  • canDelete() - Control record deletion

​
User Relationships

The Role model has a many-to-many relationship with Users: 
$role->users()       // Get all users with this role
$user->role          // Get user's assigned role
Source: app/Models/Role.php:31

​
Auditing

All user and role changes are automatically audited:
  • Creates audit log entries
  • Tracks who made changes and when
  • Records old and new values
  • View audit logs at Admin → Audits
The Role and User models implement the Auditable interface, enabling automatic change tracking.
Sources:
  • app/Models/Role.php:8
  • app/Models/User.php (standard Paymenter user model)

​
Best Practices

Principle of Least Privilege

Grant only the permissions necessary for each role’s responsibilities

Role Naming

Use clear, descriptive role names (e.g., “Billing Manager” not “Role 1”)

Regular Audits

Periodically review role permissions and user assignments

Testing

Test role permissions in a development environment before applying to production

​
Common Role Examples

Permissions for customer support staff:
  • admin.tickets.view
  • admin.tickets.update
  • admin.users.view
  • admin.services.view
  • admin.widgets.support
Permissions for billing and finance staff:
  • admin.invoices.view
  • admin.invoices.create
  • admin.invoices.update
  • admin.transactions.view
  • admin.users.view
  • admin.widgets.revenue
  • admin.widgets.overview
Permissions for managing products and services:
  • admin.products.view
  • admin.products.create
  • admin.products.update
  • admin.categories.view
  • admin.categories.create
  • admin.categories.update
  • admin.services.view
  • admin.services.update

Related Documentation

  • Dashboard - Learn about permission-based widget visibility
  • Settings - System configuration requiring admin permissions

Build docs developers (and LLMs) love

Get started for freeTalk to us