Organization admin guide
1. Register the organization
- Open Register. Enter your email, a password (the policy is shown under the field), your name, mobile, city and photo, the organization's legal name and its IIN or BIN.
- Confirm your email with the link we send. The link is valid for 48 hours. The organization is created and you are its admin.
- If the IIN/BIN is already registered, your registration becomes a join request to that organization's admins instead.
- If our staff invited you, register through the invitation link. You don't need to confirm your email.
2. Your organization area
| Dashboard | Tenants (approved, deployed, waiting), resources in force, running VMs, users, join requests and the latest events. |
| Tenants | Your tenants, and ordering a new one. |
| Users | Users of the organization, their roles and states, invitations and join requests. |
| Keys | The organization's ssh public keys. The default key goes to the gateway of every new tenant. |
| Logs | Everything that happened in the organization. |
Every list works the same way: a filter at the top, the add button on the right, actions on each row, and the details of the selected row under the list.
3. Order a tenant
| Tenant name | 4–14 lowercase latin letters and digits, unique in the organization. The tenant ID (_t_<org>_<tenant>) is built from it and can't be changed later. |
| Type | Cloud. Corporate organizations can also order corporate tenants. |
| Resources | vCPU, RAM, storage (defaults 4 / 16 GB / 100 GB), GPUs where available, backups. |
| Connections | At least one of internet, corporate network (corporate organizations only) and L2 channel. For the internet, also the bandwidth and the size of the main public network. |
| Tenant gateway | With the internet: the igw type (advanced VyOS, native Service Virtual Router, or your own VM) and, for the first two, the ssh key (your default key is offered) and the addresses allowed to connect over ssh. |
You can cancel an order while it waits for approval. When it is approved, deployment starts and the tenant page shows its progress.
4. Users
- Invite a person by email and give the role in the invitation: organization admin, read only, or tenant admin of chosen tenants. The person sets a password and photo when accepting.
- Lock / Unlock stops or restores a person's sign-in without changing anything else.
- Archive removes someone who had an account. They lose all roles and can only be invited back. Use Show archived to see them.
- Delete removes someone who never accepted their invitation.
- Join requests: users who registered with your IIN/BIN. Accept only users you know.
- Two-factor authentication is optional for tenant users. Each person turns it on in their profile.
5. Run your tenants
- Resources: request more or fewer vCPU, RAM, storage or backups. The change is applied after approval.
- Storage split: divide the storage between VM disks, images and files at any time, without approval.
- Networks: request another internet bandwidth (10–1000 Mbps), extra public networks or their removal, replace the main network, change corporate prefixes, bind an L2 channel to a network.
- Access (the tenant's secrets, kept encrypted; every look is logged): the OpenNebula console link (the platform's public FireEdge address; also the icon in the first column of the tenant list), the OpenNebula admin — show its password, Set a new password (OpenNebula changes too) or Keep the current password (checked by logging in to OpenNebula; nothing is changed) — and the igw login: address, ssh port, user and password.
- igw configurations (VyOS igw): keep the running configuration, edit a saved one (saved as a new one), apply one — over ssh, where the portal first keeps the running configuration and commits with an automatic rollback: unless you press Confirm in time (default 60 seconds; VyOS counts whole minutes), the igw goes back by itself — or by making the igw again with it. To roll back, apply the configuration kept before.
- Gateway keys: add or remove the ssh keys of the tenant gateway.
- Log: every operation on the tenant: order, approvals, deployment steps, password views and changes.
- Delete a tenant: send a deletion request. It is carried out after approval.