Types of Roles

In Advantus, different users have different levels of control, based on their roles. The Owner has the highest level of authority and control, followed by the Administrator, and so on. You can also create Custom Roles that fit your specific needs.

Key elements of RBAC include:

  • Roles: Defined based on job functions, such as Administrator, User, or Viewer.
  • Permissions: Actions or operations a role is allowed to perform (e.g., read, write, delete).
  • Users: Individuals assigned to specific roles, gaining the permissions associated with those roles.

Advantus streamlines management, enhances compliance, and reduces errors by enabling you to manage access at the role level instead of assigning permissions to individual users.

Roles and Permissions

System-based role are the pre-defined roles created by the system, each with specific a set of permissions that cannot be altered by anyone. System-defined roles are often designed to cover common use cases and provide default access controls within the application.

Advantus provides four major types of system-defined roles. These are:

RolePermissions
OwnerFull control over the organisation. Can manage billing, users, and applications.
AdminManage applications, users, and settings. Cannot access billing details.
CreatorCreate and edit content. Can view analytics within the application.
ValidatorRead-only access to view data. Can approve requests within the application.

Custom role are the roles created by the owner based on the organisation’s structure and application requirements. The permissions for these roles can vary and are fully customisable. The owner has the authority to modify or delete custom roles permanently at any time.

Note: The Owner role holds full authority within organisation, including control over billing, user management, and all applications. As this role has the highest level of access, it is critical that ownership is assigned carefully to ensure that access is not compromised.

General rules for permission access

Operation(s)Action
ReadOnly allowed to view the item or read the details.
CreateAllowed to read and create the item (e.g., create campaigns).
UpdateAllowed to read, create and update the item.
DeleteAllowed to read, create, update and delete the item.
ApproveAllowed to read the item.

Templates

Template typeOperation(s)OwnerAdminCreatorValidatorNotes
EmailRead
EmailCreate
EmailUpdate
EmailDelete
EmailApprove
WhatsAppRead-onlyWhatsApp templates are only created on WhatsApp Business Account.

Audience

Operation(s)OwnerAdminCreatorValidator
Read
Create
Update
Delete
Approve

Platform configuration(Email/SMS/WhatsApp/Web Push)

Operation(s)OwnerAdminCreatorValidator
Read
Create
Update
Delete
Approve

Campaigns (Notifications-Email/SMS/WhatsApp/Web Push)

Operation(s)OwnerAdminCreatorValidator
Read
Create
Update
Delete
Approve

Delivery

Operation(s)OwnerAdminCreatorValidator
Read - Delivery listing
Read - Campaign dashboard

Usage logs

Operation(s)OwnerAdminCreatorValidator
Read

Keys and Integration

Operation(s)OwnerAdminCreatorValidator
Read
Create
Update
Delete
Approve

Dashboard

Operation(s)OwnerAdminCreatorValidator
Read- Notification engagement metrics
Read - Total notifications analytics
Read - Track total clicks
Read - Monitor platform interaction on browsers

Note: Billing is managed at the application level, meaning each application within the organisation manages its own billing details and settings. This ensures that billing is tailored to the specific needs and usage of each app, providing greater flexibility and control over financial management.

Custom roles

The owner has the flexibility to define these roles, granting specific permissions to align with their operational needs. This approach enhances security, optimises workflow efficiency, and ensures that tasks are delegated appropriately across the team.