Administration of Users, Workspaces and Access in One Console

Add people one at a time or from a CSV file, place them in workspaces with the right roles, and deactivate accounts without losing their history. The back-office console records who did what, and when.

Book a Demo See What Is Included

Overview

One Console for the People Who Run Sover

Sover is administered from a back-office console, a web portal that runs with the rest of the platform on servers you host. Administrators add and deactivate users, organize them into workspaces and assign roles there, and role-based access control (RBAC) decides which administrator may do what.

Identity controls come with it. Two-factor authentication (2FA) is mandatory for every user, administrators can revoke a user’s sessions, and an administrative audit log records back-office actions with who made them and when.

Capabilities

What Administrators Can Do

  • Add Users One by One or in Bulk

    Create users by hand, with a check for duplicate phone numbers, or upload a CSV file that is validated as a whole before anyone is imported.

  • Manage Workspace Membership

    Add people to workspaces, remove them and change their roles in bulk, with owner, administrator and member roles in each workspace.

  • Role-Based Administration

    Four administrative roles, from Super Administrator to Staff, set what each administrator may do in the back-office console.

  • Mandatory Two-Factor Authentication

    Every user enrolls in 2FA, new users at their first login, and senior administrators can reset a user’s 2FA.

  • Sessions and Devices

    Administrators can revoke all of a user’s sessions or remove the user’s access from a single device.

  • Administrative Audit Log

    Back-office logins and actions on users and other records are logged with the initiator, IP address and time.

    Security and Compliance

Two Layers of Roles

Roles for the Console, Roles for Each Workspace

Back-office roles cover the administration of your whole Sover environment. Workspace roles apply inside one workspace. The two are distinct, so plan them separately.

Back-Office Roles

Govern the back-office console and what each administrator may do in it.

  • Super Administrator
  • Chief Administrator
  • Administrator
  • Staff

Super Administrators and Chief Administrators can reset a user’s two-factor authentication.

Workspace Roles

Set inside each workspace, shown in its member list.

  • Owner
  • Administrator
  • Member

Each workspace has its own membership and roles.

The exact permissions of each role depend on the back-office version and your deployment configuration; confirm them during setup.

How It Works

An Account from First Login to Last Day

From the first upload to the last day, an account is managed in one place.

  1. Add People

    Add users one at a time, with duplicate phone numbers caught, or upload a CSV file. The console validates the whole file before it imports anyone.

  2. Place Them in Workspaces

    Add people to workspaces, remove them and change their roles, one by one or in bulk. Each workspace has its owner, administrators and members.

  3. Secure Their Sign-In

    Every new user enrolls in two-factor authentication at first login. Administrators can sign a user out of all sessions, or out of one device.

  4. Deactivate, Keep the Record

    A deactivated user can no longer sign in, while their history and chats are kept, and uploading a CSV file again does not reactivate them. A phone-number change keeps the history too.

Security and Compliance

Included

What Is Included, and Where the Limits Are

Included

  • Back-office console. A web portal for administrators, deployed with the rest of your Sover environment.

  • User provisioning. Manual creation with a duplicate-phone check, and CSV import that is validated as a whole file.

  • Deactivation. Accounts are deactivated with their history and chats kept, and the deactivated status and date stay visible.

  • Role-based access control. Super Administrator, Chief Administrator, Administrator and Staff roles; bulk deactivation requires the relevant permission.

  • Workspace administration. Membership with owner, administrator and member roles, and settings for name, avatar, description and privacy level.

  • Sessions and devices. Administrators can revoke all of a user’s sessions or one device’s access.

  • Administrative audit log. Back-office logins and logouts, actions on users and other records with initiator, IP address and time, activations, deactivations and workspace deletions, filtered by date, event, initiator, IP address and object ID.

Stated Limits

  • Deactivation is not deletion. Deactivating an account does not erase it or its data. Whether and how accounts are deleted is confirmed for your release.

  • Permissions depend on the version. The exact permissions of each role depend on the back-office version and deployment configuration, so check the administrator responsibilities you need during setup.

  • The audit log covers administrative events. It is not a record of every message or file action. Agree the events you need, and the access, retention and export requirements, for your procurement.

  • A workspace is not a tenant. A workspace is a collaboration boundary, not a separately hosted or isolated tenant. Independent instances connect through federation.

  • Retention is set per deployment. Messages, attachments, recordings, backups and audit logs follow different retention rules, confirmed for your release and deployment.

  • 2FA policy is configured per deployment. Enrollment, enforcement and the allowed methods are set for the deployment you operate.

Where It Runs

Administration Where Accountability Matters

Government Agencies

Each ministry or agency administers its own users, workspaces and roles from a back-office console on its own servers.

Learn More

Law Enforcement

Deactivate an officer’s account without losing its chats or history, with back-office actions recorded in the audit log.

Learn More

First Responders & Alerts

Bring a whole team in from one CSV file, validated before import, and place people in the workspaces they work in.

Learn More

Keep Reading

Questions, or Ready for a Briefing?

Contact Sales

Tell us about your organization and we will arrange a briefing for your team.

The form needs JavaScript. Please enable it and reload the page.

How are administrative permissions managed?

Sover supports role-based access control and centralized administration. The exact permissions available to each role depend on the back-office version and deployment configuration, so the required administrator responsibilities should be checked during setup.

Does Sover provide administrative audit logging?

Yes. Administrative audit logging is part of Sover's control set. Agree the events you need to record and the access, retention, and export requirements; audit logging alone does not establish a complete forensic or legal-hold system.

Can administrators manage devices and sessions?

Yes. Sover includes device and session management. Use those controls as part of your access policy, and confirm the supported actions and client behavior for the deployment you operate.

Can different departments have different workspace members?

Yes. Workspaces have their own membership and roles, allowing teams to organize their conversations separately. A workspace is a collaboration boundary; it should not be treated as proof of a separately hosted or isolated tenant.

Is a workspace the same as a separate Sover instance?

No. A workspace organizes collaboration within an environment. An instance is a deployment of the platform. Use federation when independently operated instances need to communicate under agreed policies.