Skip to main content

User types

The following user types are used to access resources and account settings:

  • Account owner — the primary user, created automatically when the account is registered;
  • users — invited by the Account owner and have limited access to the Control panel;
  • service users — added by the Account owner, used for programmatic access and API access. They do not have access to the Control panel.

Access for users and service users is determined by permissions that have been assigned to them.

Learn more about authenticating different user types in the API in the API Request Authentication API documentation.

Account owner

The primary user who registered the account. Has access to all products, services, resources, and account settings.

The Account owner has exclusive permissions that cannot be assigned to other users:

You cannot assign another user as the Account Owner or change their permissions. You can only change their profile details.

Users

A user with an account in the Control Panel, invited to the account by the Account Owner or a user with the iam.admin role. A user account is managed by a real person (human identity).

The level of access is determined by the permissions assigned to them.

Users can authenticate in the Control panel in two ways:

  • via email and a password created in the Control Panel. They undergo two-factor authentication via email and can generate a static token (X-Token) for full access to Servercore product APIs;
  • via SSO on the identity provider side if they belong to one of the federations. They do not undergo two-factor authentication. Users are added as already registered—they only need to enter their full name upon their first login. An email address is mandatory for them. They do not have access to the API.

Service users

A user with an account intended for programs, services, automation, and access via Servercore product APIs. They do not have access to the Control Panel and only have a login and password. This is a machine account (non-human identity).

The level of access is determined by the permissions assigned to them.

The Account Owner or users with the iam.admin role can add service users and issue access keys to them—SSH, S3, and ADB keys.