Skip to content
English
Go to caxton.io
  • There are no suggestions because the search field is empty.

Caxton Corporate Roles Comparison

Read a clear and structured table summarising the 'roles' to manage your Caxton corporate account and their functionalities.

Caxton Corporate Roles Comparison

Here’s a clear and structured table summarising the 'roles' and their functionalities:

Role Name Code Description Permissions / Notes
CardUser 0 Standard cardholder Can submit ATM expenses (only on specific page); access wallet balance, personal history, and "My Expense" page. Not submittable by admin.
Signatory 1 Legacy role No longer used; may appear for older clients.
Administrator 2 Full admin Likely full access to manage users, wallets, transactions, and settings.
Owner 3 Account/business owner Likely has top-level control, similar to or above admin.
ShortFormStarter 7 Initial applicant Can log in to complete the application.
InputterAccount 9 IP-only role for specific client View-only access except bulk payments page (can upload files unless restricted by MLA).
WalletGroupManager 10 Scoped admin Admin-like access limited to assigned wallets; can manage cards.
CorporateViewer 11 Viewer role for IP & EM Can view all pages but cannot perform any actions.
CorporateApprover 12 Bulk approver Can approve file uploads only.
Multi Roles — Role-switching interface Allows users to switch between roles or cards via a dedicated page.

 

Role Can View Account Info Can Initiate Payments Can Approve Payments Card Spending
Corporate Inputter ✅ Yes ✅ Yes ❌ No ❌ No
Corporate Viewer ✅ Yes ❌ No ❌ No ❌ No
Corporate Approver ✅ Yes ❌ No ✅ Yes ❌ No
Card User ✅ Limited (own card) ❌ No ❌ No ✅ Yes

Key Differences:

  • Inputter: Prepares transactions but cannot authorise them.
  • Viewer: Read-only access for oversight or auditing.
  • Approver: Grants final approval for payments but does not create them.
  • Card User: Operates a prepaid/corporate card for expenses; no access to company-level payments.

 

Corporate Inputter

  • Purpose: Initiates transactions.
  • Capabilities:
    • Can create payment instructions or card load requests.
    • Cannot approve or release payments.
  • Use Case: Often used for finance staff who prepare payments but don’t authorise them.

Corporate Viewer

  • Purpose: Read-only access.
  • Capabilities:
    • Can view balances, transactions, and reports.
    • Cannot create, edit, or approve any instructions.
  • Use Case: Ideal for auditors or managers who need oversight without operational control.

Corporate Approver

  • Purpose: Authorises transactions created by inputters.
  • Capabilities:
    • Can approve or reject payment instructions.
    • Cannot initiate payments themselves (unless combined with inputter rights).
  • Use Case: Typically senior finance or compliance roles.

Card User

  • Purpose: Operates a prepaid or corporate card.
  • Capabilities:
    • Can spend funds within assigned limits.
    • Usually has access to view their own card activity.
    • No authority over company-level payments or approvals.
  • Use Case: Employees who need to make purchases or travel expenses.