Create user roles based on the specific persons/applications/roles that will need access to your Realtime Register account.

The sixth step is to create designated user roles that you connect to the designated users in your Realtime Register account.

In your Realtime Register account, you are able to create user roles with multiple levels of access corresponding to the required actions a user/application needs access to. It's advised to first create user roles that correspond to the roles certain users or even applications have within your organisation that need access to your Realtime Register account.

For example, you can create a WHMCS user role that only has access through API if you use WHMCS to manage your customer domains. You can create a support level one, level two, and level three user role to assign to your first, second and third line support employees. A user role is defined as a set of permissions that can be connected to any of the users that you create in your account. Once the user roles are created, you can create users and assign the corresponding user roles that match the user access criteria. For an instruction on creating user roles, read on below.

Take note: it's advised to first create user roles for all possible roles in your organization prior to creating person/application specific users.

Once logged in, you'll reach the page below on which all active user roles are detailed and which are active in your account by default.

The admin user role is connected to your admin user, we strongly recommend to not make any changes to this user role and only assign this user role to the admin user.
The all user role is a user role that is assigned to your admin user as well, and as the name suggests; this is a role that contains all permissions except for the PREMIUM_DOMAIN user role and ADAC_ACCES role in case ADAC is activated for your account.

Take note: Do not make any changes to the admin and all user roles, simply keep them assigned to your admin user and create new user roles with specific rights to assign to users you are going to create yourself. The admin user is designed for the administrator of the account and can be used when other users have lost access to their account and need their passwords/MFA reset for example.

Before you dive into creating user, give some thought to the different users that will need access to your Realtime Register account to manage domain registrations/transfers/renewals for your organisation. The most common user roles used for various resellers we provide our services to are;

Support lvl. 1 user role
Support lvl. 2 user role
Support lvl. 3 user role
Finance user role
API (application specific) user role
ISproxy user role

Of course, user roles can be named and necessary for various other positions in your organisation, but the above list should provide enough instruction to determine which user roles you should create for your organisation specifically. Once you've worked out which user roles you need for your organisation, you can move ahead below and start to create them. In the example below we'll create a Finance user and a user for an application that needs access through API.

Finance user role

API user role

Create a finance user role

To create a new user role, click "+ New user role"

Submit your password

Next, give the user role a distinctive name, in this case Finance would suffice. Select the permissions under the Financial permissions section > "View Billing" "Deposit" and under the General permissions section you'll need the "View Process permission".

Take note: it is essential to put a check at the VIEW_PROCESS permission because processes are used throughout the whole Realtime Register Domain Manager.

Once selected, click "create user role" to create the user role.

You've now successfully created a finance user role with permissions to View the billing part of the Domain Manger and make deposits to add funds to your account balance.

Create an API user role

To create a new user role, click "+ New user role"

Submit your password

Next, give the user role a distinctive name, in this case you could use 'API' for example. Based on which parts of our systems the user role needs access to, you will select the permissions. In this example all the parts that hit domain & SSL management are used. This translates to all options under the Domains, Hosts, Contacts, SSL certificates and DNS templates permissions are selected.

Once selected, click "create user role" to create the user role.

You've now successfully created a user role with permissions that are required to manage Domains & SSL certificates through the API.

You can use the above instructions to create other users as well. In case you are creating user roles for your support staff, keep in mind that the VIEW_PROCESSES permission is a requirement to be able to view and access any type of domain, SSL or contact process in the Domain Manager. You are responsible yourself for determining which user roles should have access to which permissions. Once you've created all the user roles you need, you can move on to creating users and assigning the user roles to the designated users that the user roles were designed for in the first place.