Написать в техподдержку Позвонить нам
Admin Panel Logout

In this article:

    Projects, users and roles

    As an administrator, you manage projects, users, and roles. Projects are organizational units in the cloud that you can assign users to. Users can be members of one or more projects. Roles determine what actions users can take. The role assignment is made for the user-project pair.


    A project is a group of one or more users. In Cloud Computing, a project owns virtual machines. In Object Storage, a project owns buckets. Users can be associated with more than one project. Each project and pair of users can have a role associated with it.

    You can manage projects, users and roles independently of each other.

    During the initial project setup (registration), at least one project, user and his role are defined.

    You can assign users to one or more projects, and change or remove the assignment.

    Project creation

    Additional projects can be created for the purpose of sharing resources, roles, or other architectural features of the tasks being implemented.

    You can create a project in your personal account in the page header. When creating a new project, the current user gets the role of the Project Owner, regardless of his role in the current project:


    The name of the project should consist only of lowercase letters of the Latin alphabet and numbers, be from 4 to 60 characters long. The symbols ".", "_", "-" (except for the first and last characters) are allowed.

    Modifying project data

    To rename a project, select your project from the drop-down list in the header of your personal account page, and click on the "Pencil" tool to rename:

    Changing the title in the title will change the display name of the project.


    Pay attention to the button next to the "Pencil". It allows you to copy the project name for use in the API, CLI or when submitting a request to technical support.

    To change additional information about the project, use the "Project Settings" menu:

    In the project settings menu, you can fill in the data of an individual or legal entity, as well as download configuration files to access the MCS platform through the developer tools (API) and infrastructure management (Terraform).

    Change of owner

    If it becomes necessary to change the project owner (for example: complete loss of access to the owner's account), you should contact technical support to change the roles of project participants. In this case, the project must have a second account, the owner of which submits an application.

    Change of ownership is made after verification of project data and participant accounts by technical support staff.


    It is recommended to use corporate mailboxes when registering on behalf of a legal entity. This will greatly simplify the verification procedure and will allow you to restore access to the project without the need to contact support.

    Freeze the project

    Upon reaching the zero balance, the project resources will be automatically stopped until the project balance is replenished. In this state, API tools for Object Storage are partially available. After replenishing the balance, billing tools will allow you to use the services again, but you will need to manually launch each resource.

    This mechanism allows you to prevent the presence of unconscious additional costs on the project, it is especially useful if there is a linked automatic replenishment or post-pay settlement method.

    If it is necessary to "freeze" the project, i.e. suspend debiting of funds, then in this case stop all virtual machines and delete resources that fall under automatic billing: disks, buckets, backups, etc. With this approach, you can save some of the resources of your project for a while if you plan to return to using the MCS platform later. There are no other ways to freeze the project.

    Deleting project data

    In the absence of a positive balance recovery, the project resources will be queued for deletion, depending on the availability of payments for the entire period of the project's existence:

    • If there were no cash flows in the project, then after 3 days all resources will be deleted;
    • If the payment was made, then the resources will be placed in the queue for deletion after 30 days (or upon reaching the balance equal to -1000 rubles) after the services were stopped.

    The delete queue is a mechanism for cleaning up resources, in which data from the project and the MCS platform are deleted irrevocably, without any possibility of their recovery.

    Transferring resources between projects

    Within the MCS platform, there is a limited set of opportunities for transferring resources between projects. It is possible to transfer data from one project to another for Disks.

    Deleting a project

    Deleting a project is possible through a request to technical support on behalf of the owner of the deleted project. Before deleting a project, you need to make sure that there are no associated automatic payment methods, and that all necessary data has been exported from the project. To execute the request, you must specify the name of the deleted project.


    In your MCS personal account, you can add additional project participants who will have access to work with cloud services. When added, the role of the participant is indicated.

    Adding a role

    To add, go to the "Access Control" section in the MCS panel:

    Add a participant and enter his details:

    • email address;
    • name;
    • roles in the project.

    The contributor you add can have multiple roles in the project. If there are two different roles, mutually exclusive access levels, the permissive role will be applied to perform actions on project objects.

    Upon completion of adding a user, the participant will receive an email, which will confirm the actions of adding:

    To activate the invitation, follow the link in the letter, create a password and enter your MCS account with it.

    Role matrix

    The mcs platform supports the differentiation of access rights to project resources based on a role model.

    There are six predefined roles available. Below is a list of roles and their corresponding permissions.

    List of roles and permissions:

    Role Rights
    Project owner Has access to read / change / delete all project resources, including the section "user management" and "payment settings"
    Super administrator The super administrator has the ability to read / modify all project resources and the ability to add new administrators.
    Project administrator The project administrator has the ability to read / change / delete project resources. Without the ability to manage users.
    Billing administrator The billing administrator has access only to the Billing menu item. Can change payment details. The rest of the services that are connected in the project are not shown to the user with this role
    Security Administrator The Security Administrator allows you to add new users to the project, assign them roles.
    Network administrator The network administrator has access to the menu items for creating a network and managing router rules.
    Observer The observer can view information in all services of the project. But cannot change or add resources.

    Removing a member

    In your personal account, in the "Users" and "Roles" tabs, you can not only add, but also remove members.

    Select the desired participant and click Remove, then confirm your choice.


    If you delete the user on whose behalf the Kubernetes cluster was created, after restarting it, a malfunction will occur. To restore operation, add the user on whose behalf the cluster was created and restart the cluster.

    Was this article helpful?