Skip to main content
Skip table of contents

User Roles

Click to view full screen

The RealWell platform uses role-based access control to ensure users only have access to the tools and information needed for their responsibilities.

This guide explains the available user roles and their permissions.

Role

Description

Permissions

Account Admin

The primary administrator for your organisation’s RealWell account.

  • Full access to manage users, apps, and billing.

  • Can invite, edit, or remove users.

  • Manages app activations and quota increases and handles billing and payments.

Account User

Standard users of the platform, typically staff or practitioners who need access to the apps.

  • Basic access to assigned apps.

  • Cannot manage users, apps, or billing.

Account User+

Enhanced user role for those needing additional in-app functions beyond the basic Account User role.

  • Access to apps plus oversight of account users in PEEM

  • Cannot manage users, apps, or billing.

Billing Admin

Designated user responsible for financial and subscription management.

  • Full access to the Apps & Billing section.

  • Can manage payment methods, view/download invoices, and adjust quotas.

  • Cannot access apps or manage users.

Recovery Admin

Backup administrator to ensure secure continuity if the Account Admin is unavailable or leaves.

  • Can manage users, approve access requests, and maintain secure access.

  • Does not manage billing unless also assigned Billing Admin - Intended for security and recovery scenarios.

Key Notes

  • Each organisation must have at least one Account Admin.

  • It is recommended to assign the Recovery Admin for business continuity.

  • Billing Admins and Account Admins both have access to billing, but only Account Admins can manage users.

  • Account User+ provides flexibility where staff require more than standard app access but do not need administrative rights.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.