Team users, roles and permissions

In the Console every colleague has their own account and a role that decides what they see and what they can do. You build those roles, either starting from the four ready-made ones or from scratch.

Creating an account for a colleague

1. Open Users from the left menu.
2. Click Add at the top right.
3. Fill in Firstname, Lastname and Email address in the Personal details box.
4. Type a New Password of at least eight characters. No invitation email goes out, you pass the password to your colleague yourself.
5. In the Role & access box pick the role from the Role dropdown.
6. Click Save. Your colleague shows up in the list with their role next to the name.

After saving, the email address can no longer be edited from this screen and the password cannot be reset from here. Your colleague changes it from their own Profile, by typing the current one.

Your own account is marked Account owner and cannot be moved to another role.

The four ready-made roles

Role	What it can do
Administrator	everything, it is the owner’s role
Technician L1	looks at DRs, VMs, connectors and customers, works tickets, configures notifications
Technician L2	everything Technician L1 does, plus managing DRs (initiate, restore, schedules, credentials, console), VMs and connectors
Administrative	customers, tickets, billing and purchases

You can edit them as you like, except Administrator, which cannot be renamed or deleted.

Building a custom role

1. Open Roles & Permissions from the menu.
2. Click Add Role.
3. Type the role name in the field at the top of the page.
4. Switch on the toggles in the boxes you need. There are nine of them, namely Disaster Recovery, Virtual Machines, Connectors, Customers, Users, Support, Billing, Logs and System. Hover a toggle to read what it unlocks.
5. Click Save.

Changes to a role apply straight away to whoever already holds it, with no need to log in again.

The permissions that switch themselves on

Some permissions need another one to make sense, and the Console adds it for you when you save. Switch on DR management and you also end up with permission to view DRs. The same happens for VMs, for connector orchestration which requires the connector view, and for managing customers, users and tickets. Configuring notifications switches on the DR view too, because the alerts are about DRs.

Assigning a role

The quick way is the Roles & Permissions page. Every role is a card with its own Members list, so drag a colleague from the card they sit in onto the card of the role you want to give them and the permissions change instantly. The owner cannot be dragged.

Otherwise open the colleague from Users and change the Role dropdown.

To delete a role use the three-dot menu on its card. Whoever held it is left with no permissions until you assign them another role.

What stays out

Not everything can be delegated, a few actions stay with Sefthy even for the owner.

• Detaching a connector from a VM. A partner can attach one, not remove it.
• Commercial discounts on the plans, which you see already applied on the invoice but do not manage from the partner Console.
• Accessing someone else’s account for support, which is reserved to Sefthy staff and stays logged.

The permission palette also leaves out some fine-grained commands on customer VMs, networks, ISOs and public IP addresses among them. Those stay with the customer or with Sefthy staff.