User Management in rConfig V8 Core

User management in rConfig V8 Core controls who can sign in to the application. After reading this page you can create and edit local user accounts, approve users who sign in through SSO, and remove accounts you no longer need. You will also know where role-based access control sits, because per-user roles are a Pro, Enterprise, and Vector feature rather than a V8 Core capability.

When to use this

Go here when you are setting up accounts for your team, removing the default admin account on a fresh install, or approving a colleague who has just signed in through SSO for the first time. The Users page is also where you check who currently has access.

Prerequisites

• An administrator account in rConfig V8 Core.
• For SSO approvals, a working SSO connection. See SSO overview for setup.

How access works in V8 Core

V8 Core has a single access level. Every authenticated user has the same access to the application and to managed devices. There are no per-user roles to assign, and no permission to grant or withhold on an individual account.

Per-user roles and RBAC are a Pro feature

Role-based access control (RBAC), tag-scoped device visibility, and per-user permissions are part of the rConfig Pro, Enterprise, and Vector editions, not V8 Core. To scope what each user can see and do, see the rConfig Pro documentation. On V8 Core, control access by limiting who holds an account.

Local users and SSO users

V8 Core supports two ways for a user to sign in:

• Local users are created directly in rConfig with a username and password stored in the rConfig database. They are active as soon as you save them. Use these for small deployments and lab environments.
• SSO users sign in through a Single Sign-On provider (SAML or OAuth). Their account is created automatically on first successful sign-in, then waits for administrator approval before they can use the application.

Once signed in, both types of user have the same access.

The SSO approval workflow

SSO accounts do not become active on their own. The workflow keeps account creation under administrator control:

1. The user signs in successfully through SSO.
2. rConfig creates the account in a pending state.
3. The user cannot use rConfig until an administrator approves the account.
4. The administrator reviews pending users and approves the legitimate ones.
5. The approved user gains access.

Note

Local users created by an administrator skip the approval workflow and are active immediately. Only SSO users wait for approval after their first sign-in.

Open the Users page

1. Select Users from the main navigation menu.
2. Review the list of accounts, showing username, email, and status.
3. Use the search and filters to find a specific user.
4. Use the row action icons to edit, approve, or delete an account.

Create a local user

1. On the Users page, click New User.
2. Enter a Username. This is the login identifier (alphanumeric, no spaces).
3. Enter a valid, unique Email address.
4. Enter a strong Password, then re-enter it in Confirm Password.
5. Optionally disable email notifications if this user should not receive system alerts.
6. Click Save.

The new user can sign in immediately with the credentials you set.

Remove the default admin account

A fresh V8 Core install includes a default admin account (admin@domain.com). Create a new administrator account with your own email address, sign in as that account, then delete the default account. Leaving a well-known default account active is a serious security risk.

Edit a user account

1. On the Users page, find the user to change.
2. Click the edit icon in the user row.
3. Update any field except the username, which cannot be changed.
4. To reset the password, enter a new one in both password fields.
5. Toggle the notification preference if needed.
6. Click Save.

Changes take effect immediately.

Approve an SSO user

1. Open the Users page. Pending accounts show a pending status.
2. Verify the account before approving:
   • Confirm the email domain matches your organisation.
   • Confirm the person should have rConfig access.
3. Click the approve icon in the user row.
4. The user is notified and can now sign in.

To reject a pending account, click the delete icon. A rejected user cannot sign in.

Tip

Agree a simple approval routine for SSO sign-ins: who approves, how they verify the person, and a target turnaround (for example within one working day). A documented routine keeps approvals consistent.

Disable email notifications

1. Edit the user account.
2. Toggle Email Notifications off.
3. Click Save.

With notifications off, the user no longer receives device connection failure alerts, scheduled task notifications, or system announcements by email. They can still see everything in the web interface.

Delete a user account

1. On the Users page, find the user to remove.
2. Click the delete icon in the user row.
3. Confirm when prompted.

Common gotchas

• Deleted accounts cannot be recovered. Confirm you have the right user first.
• You cannot delete the account you are currently signed in as, and at least one administrator must always exist. To remove the default admin, create another admin account, sign in as it, then delete the default.
• Username is permanent. If a user needs a different login name, create a new account and delete the old one.
• A user whose access you changed may need to sign out and back in for the change to take effect.

Where authentication events are logged

Sign-in attempts, failures, and other authentication events are recorded in the Application Log, not on the Users page. Review it to spot repeated failed sign-ins, sign-ins outside normal hours, or access from accounts that should have been removed.

What’s next

• SSO overview sets up Single Sign-On so users can authenticate through your identity provider.
• Application Log shows authentication events and the wider audit trail.
• Security hardening covers account, credential, and platform hardening for V8 Core.