tarantool · maryiaLichko · May 12, 2026 · May 12, 2026 · May 12, 2026 · May 13, 2026
diff --git a/doc/tooling/tcm/_images/tcm_ui_acl.png b/doc/tooling/tcm/_images/tcm_ui_acl.png
diff --git a/doc/tooling/tcm/_images/tcm_ui_add_ons.png b/doc/tooling/tcm/_images/tcm_ui_add_ons.png
diff --git a/doc/tooling/tcm/_images/tcm_ui_audit_log.png b/doc/tooling/tcm/_images/tcm_ui_audit_log.png
diff --git a/doc/tooling/tcm/_images/tcm_ui_cluster_metrics.png b/doc/tooling/tcm/_images/tcm_ui_cluster_metrics.png
diff --git a/doc/tooling/tcm/_images/tcm_ui_cluster_migrations.png b/doc/tooling/tcm/_images/tcm_ui_cluster_migrations.png
diff --git a/doc/tooling/tcm/_images/tcm_ui_instance_explorer.png b/doc/tooling/tcm/_images/tcm_ui_instance_explorer.png
diff --git a/doc/tooling/tcm/_images/tcm_ui_tcm_metrics.png b/doc/tooling/tcm/_images/tcm_ui_tcm_metrics.png
diff --git a/doc/tooling/tcm/_images/tcm_ui_tuples.png b/doc/tooling/tcm/_images/tcm_ui_tuples.png
diff --git a/doc/tooling/tcm/_images/tcm_ui_user_settings.png b/doc/tooling/tcm/_images/tcm_ui_user_settings.png
diff --git a/doc/tooling/tcm/_images/tcm_ui_users.png b/doc/tooling/tcm/_images/tcm_ui_users.png
diff --git a/doc/tooling/tcm/tcm_access_control/tcm_access_control_rbac.rst b/doc/tooling/tcm/tcm_access_control/tcm_access_control_rbac.rst
@@ -412,3 +412,24 @@ The following cluster permissions are available in |tcm|:
 
     *   -   ``cluster.metrics``
         -   View cluster metrics
+
+    *   -   ``cluster.config.security``
+        -   View and edit settings on the **Security** tab
+
+    *   -   ``cluster.user.read``
+        -   View users and roles of the cluster on the Users tab on the instance page
+
+    *   -   ``cluster.user.write``
+        -   Create, edit, and delete users and roles of the cluster on the **Users** tab on the **Instance page**
+
+    *   -   ``cluster.migrations.read``
+        -   View information about loaded and applied migrations on the **Migrations** tab
+
+    *   -   ``cluster.migrations.write``
+        -   Create, edit, and apply migrations
+
+    *   -   ``cluster.tcf.read``
+        -   View information about TCF clusters and their status on the **TCF** tab
+
+    *   -   ``cluster.tcf.write``
+        -   Modify TCF configuration settings and switch cluster states on the **TCF** tab
diff --git a/doc/tooling/tcm/tcm_access_control/tcm_ldap_auth.rst b/doc/tooling/tcm/tcm_access_control/tcm_ldap_auth.rst
@@ -101,6 +101,7 @@ Define the general configuration settings:
 *   **Automatically add non-existent users**. By default, |tcm| automatically saves
     LDAP user information to its :ref:`backend store <tcm_backend_store>`
     upon their first login. Turn the toggle off if you don't want to save users from this LDAP server.
+    If the parameter is disabled, the user must be added manually in TCM on the **Users** tab, and the authentication method must be set to LDAP.
 
 ..  _tcm_ldap_auth_config_connect:
 
@@ -122,7 +123,7 @@ LDAP queries
 To define how |tcm| queries the LDAP server for user authentication and authorization,
 fill in the fields of the **Queries** step:
 
--   **Query user** and **Query password**. Credentials of the LDAP user on behalf
+-   (Optional fields) **Query user** and **Query password**. Credentials of the LDAP user on behalf
     of which all LDAP queries are executed: a distinguished name (DN) and a password.
     Example DN:
 
@@ -163,7 +164,7 @@ fill in the fields of the **Queries** step:
 
 -   (Optional) **Template query**. A template for querying the LDAP server for the DN. This
     way is used if **Template DN** is not provided.
--   **Group query template**. A template for querying groups to which a user belongs
+-   (Optional) **Group query template**. A template for querying groups to which a user belongs
     for authorization purposes. Learn more in :ref:`tcm_ldap_auth_config_permissions`.
     Example:
 

diff --git a/doc/tooling/tcm/tcm_audit_log.rst b/doc/tooling/tcm/tcm_audit_log.rst
@@ -37,9 +37,15 @@ For details, see :ref:`Viewing audit log <tcm_audit_log_view>`.
 Enabling audit logging
 ----------------------
 
-To enable audit logging in |tcm|, go to **Audit settings** and click **Enable**.
+You can enable and configure the audit log in two ways:
 
-To additionally send audit log events to the standard output, click **Send to stdout**.
+*   in the TCM UI
+*   in the TCM configuration YAML file
+
+To enable audit logging in |tcm| UI, go to **Audit settings** and click **Enable**. To additionally send audit log events to the standard output, click **Send to stdout**.
+
+You can also pre-configure audit logging during the first TCM launch by setting options in the TCM configuration file (tcm.yaml)
+through the :ref:`initial-settings.auditlog <tcm_configuration_initial>` parameter.
 
 ..  _tcm_audit_log_config:
 
@@ -56,7 +62,7 @@ Writing to a file
 To write |tcm| audit logs to a file:
 
 1.  Go to **Audit settings** and select the **file** protocol.
-2.  Specify the name of the audit log file. The file appears in the |tcm| working directory.
+2.  Specify the name of the audit log file. The file will be saved in the directory specified by the user, which can be either absolute or relative. The file appears in the |tcm| working directory.
 3.  Configure the log files rotation: the maximum file size and age, and the number
     of files to store simultaneously.
 4.  (Optional) Enable compression of audit log files.

diff --git a/doc/tooling/tcm/tcm_configuration.rst b/doc/tooling/tcm/tcm_configuration.rst
@@ -68,13 +68,10 @@ The example below shows a fragment of a |tcm| configuration file:
 
     # a fragment of a YAML configuration file
     cluster: # top-level group
-        on-air-limit: 4096
         connection-rate-limit: 512
         tarantool-timeout: 10s
         tarantool-ping-timeout: 5s
     http: # top-level group
-        basic-auth: # nested group
-            enabled: false
         network: tcp
         host: 127.0.0.1
         port: 8080