Skip to main content

Manage access to Cloud for 1C

Access to Cloud for 1C is regulated by:

For access via the API, use keys.

Learn more about access management in the Access management in Selectel products instructions.

Access within roles

Access to Cloud for 1C is granted by Cloud for 1C roles and global roles. Learn more in the Role reference instructions.

Role groupRoleAccess
Cloud for 1C rolesgo1c.adminManage Cloud for 1C resources
go1c.viewerView Cloud for 1C resources
Global rolesmemberManage Cloud for 1C resources and other products, account, billing, and projects
billingManage billing for Cloud for 1C and other products
iam.adminManage access to Cloud for 1C and other products
iam.viewerView access to Cloud for 1C and other products
readerView Cloud for 1C and other product resources, account, billing, and projects

Cloud for 1C roles

go1c.admin

The go1c.admin role grants access to managing Cloud for 1C resources. It does not have access to other products.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations in Cloud for 1C

In the Account access scope:

  • manage 1C server clusters in all projects:

    • create a server cluster;
    • scale a cluster;
    • change cluster settings (enable automatic disk scaling, web server, web publication, and debug mode; manage IP address allowlist for accessing web publications; add custom domains);
    • storage management (connecting and disconnecting S3 buckets) *;
    • connecting to a private network **;
    • rent 1C licenses;
    • change maintenance window;
    • terminate user sessions;
    • restart a cluster;
    • delete a cluster;

  • manage info-bases in all projects:

    • create an info-base;
    • uploading an infobase from a .dt file *;
    • manage scheduled job execution;
    • configure user sessions (block, allow, terminate);
    • create a backup;
    • change web publication configuration;
    • delete an info-base;

  • manage databases in all projects:

    • create databases;
    • scale a database;
    • manage automatic disk scaling;
    • change maintenance window;
    • delete a database;

  • manage backups in all projects:

    • creating backup storage *;
    • editing storage *;

  • manage Prometheus tokens for collecting metrics in all projects

In the Project access scope:

  • manage 1C server clusters in your project:

    • create a server cluster;
    • scale a cluster;
    • change cluster settings (enable automatic disk scaling, web server, web publication, and debug mode; manage IP address allowlist for accessing web publications; add custom domains);
    • storage management (connecting and disconnecting S3 buckets) *;
    • connecting to a private network **;
    • rent 1C licenses;
    • change maintenance window;
    • terminate user sessions;
    • restart a cluster;
    • delete a cluster;

  • manage info-bases in your project:

    • create an info-base;
    • manage scheduled job execution;
    • configure user sessions (block, allow, terminate);
    • create a backup;
    • change web publication configuration;
    • delete an info-base;

  • manage databases in your project:

    • create databases;
    • scale a database;
    • manage automatic disk scaling;
    • change maintenance window;
    • delete a database;

  • manage backups in your project:

    • creating backup storage *;
    • editing storage *;

  • manage Prometheus tokens for collecting metrics in your project

* To manage the connection of backup storage, cluster data storage, and uploading an infobase from a .dt file, a combination of roles is additionally required: s3.admin and iam.admin.

** To manage the cluster connection to a private network that has already been created in the project, the vpc.private_network.viewer role is additionally required.

go1c.viewer

The go1c.viewer role grants view access to everything managed by go1c.admin.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations in Cloud for 1C

In the Account access scope:

  • view 1C server clusters in all projects;
  • view info-bases in all projects;
  • view databases in all projects;
  • view backups in all projects;
  • view a list of generated Prometheus tokens for collecting metrics in all projects

In the Project access scope:

  • view 1C server clusters in your project;
  • view info-bases in your project;
  • view databases in your project;
  • view backups in your project;
  • view a list of generated Prometheus tokens for collecting metrics in your project

Global roles

member

The member role grants full access to all services. It does not grant access to managing Control panel users, service users, user groups, and federations.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations in Cloud for 1C

In the Account access scope:

  • manage 1C server clusters in all projects:

    • create a server cluster;
    • scale a cluster;
    • change cluster settings (enable automatic disk scaling, web server, web publication, and debug mode; manage IP address allowlist for accessing web publications; add custom domains);
    • storage management (connecting and disconnecting S3 buckets) *;
    • connect to a private network;
    • rent 1C licenses;
    • change maintenance window;
    • terminate user sessions;
    • restart a cluster;
    • delete a cluster;

  • manage info-bases in all projects:

    • create an info-base;
    • uploading an infobase from a .dt file *;
    • manage scheduled job execution;
    • configure user sessions (block, allow, terminate);
    • create a backup;
    • change web publication configuration;
    • delete an info-base;

  • manage databases in all projects:

    • create databases;
    • scale a database;
    • manage automatic disk scaling;
    • change maintenance window;
    • delete a database;

  • manage backups in all projects:

    • creating backup storage *;
    • editing storage *;

  • manage Prometheus tokens for collecting metrics in all projects;

  • manage projects, their limits, and quotas;

  • manage billing in all projects

In the Project access scope:

  • manage 1C server clusters in your project:

    • create a server cluster;
    • scale a cluster;
    • change cluster settings (enable automatic disk scaling, web server, web publication, and debug mode; manage IP address allowlist for accessing web publications; add custom domains);
    • storage management (connecting and disconnecting S3 buckets) *;
    • rent 1C licenses;
    • change maintenance window;
    • terminate user sessions;
    • restart a cluster;
    • delete a cluster;

  • manage info-bases in your project:

    • create an info-base;
    • manage scheduled job execution;
    • configure user sessions (block, allow, terminate);
    • create a backup;
    • change web publication configuration;
    • delete an info-base;

  • manage databases in your project:

    • create databases;
    • scale a database;
    • manage automatic disk scaling;
    • change maintenance window;
    • delete a database;

  • manage backups in your project:

    • creating backup storage *;
    • editing storage *;

  • manage Prometheus tokens for collecting metrics in your project;

  • manage limits and quotas in your project;

  • manage billing in your project

* To manage the connection of backup storage, cluster data storage, and uploading an infobase from a .dt file, the role iam.admin is additionally required.

billing

The billing role grants access to billing management without access to service management.

Access scopesAccount
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations in Cloud for 1C
  • manage billing;
  • view rented 1C licenses;
  • view Cloud for 1C consumption

iam.admin

The iam.admin role grants access to user management. It does not grant access to services, billing, or managing one's own account: changing permissions, managing notifications, or deleting a user. The first user with the iam.admin role is created by the Account Owner.

Access scopesAccount
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations in Cloud for 1CManaging users, service users, and user groups

iam.viewer

The iam.viewer role grants view access to everything managed by iam.admin.

Access scopesAccount
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations in Cloud for 1CViewing Control panel users, service users, and user groups

reader

The reader role grants view access to everything managed by member in the same scope.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations in Cloud for 1C

In the Account access scope:

  • view 1C server clusters in all projects;
  • view info-bases in all projects;
  • view databases in all projects;
  • view backups in all projects;
  • view a list of generated Prometheus tokens for collecting metrics in all projects;
  • view projects, their limits, and quotas;
  • view billing data and consumption

In the Project access scope:

  • view 1C server clusters in your project;
  • view info-bases in your project;
  • view databases in your project;
  • view backups in your project;
  • view a list of generated Prometheus tokens for collecting metrics in your project;
  • view limits and quotas in your project;
  • view billing data and consumption in your project

Keys for API access

Depending on the API type, you will need: