diff --git a/docs/dns-client/configuration.md b/docs/dns-client/configuration.md
index 6f65ad636..942d0713d 100644
--- a/docs/dns-client/configuration.md
+++ b/docs/dns-client/configuration.md
@@ -102,10 +102,41 @@ The `upstream` object configures the actual resolving of requests. It has the fo
 
 - `groups`: The set of upstream servers keyed by the group’s name. It has the following properties:
 
-    - `address`: The upstream server’s address.
+    - `address`: The upstream server’s address. If `autodevice.enabled` set to `true` for this group, the address should be a URL with one of `https`, `tls`, or `quic` scheme.
 
       **Example:** `'8.8.8.8:53'`
 
+    - `autodevice`: Represents an automatic connection of a device.
+
+      :::note
+
+      The autodevice option must be used only for AdGuard DNS upstreams. Otherwise, we can’t guarantee proper work.
+
+      :::
+
+      It has the following properties:
+
+        - `enabled`: Defines whether all clients within the current group can be connected automatically.
+
+          :::info
+
+          The predefined `private` group must have `enabled` set to false, as it doesn't support autodevice yet.
+
+          :::
+
+        - `profile_id`: [ID of a profile][profile-id], in which new devices will be added.
+
+        - `device_type`: A [type of device][device-type] which will be created for new clients.
+
+      **Property example:**
+
+      ```yaml
+      'autodevice':
+          - enabled: true
+          - profile_id: 'defa5678'
+          - device_type: 'lnx'
+      ```
+
     - `match`: The list of criteria to match the request against. Each entry may contain the following properties:
 
         - `question_domain`: The domain or a suffix of the domain that the set of upstream servers should be used to resolve.
@@ -134,7 +165,7 @@ The `upstream` object configures the actual resolving of requests. It has the fo
 
   :::info
 
-  `groups` should contain at least a single entry named `default`, and optionally a single entry named `private`, both should have no `match` property.
+  `groups` should contain at least a single entry named `default`, and optionally a single entry named `private`, both should have no `match` property. The `private` group is also used to define the HumanID for clients created by `autodevice` feature. If it is not defined, an alternative generation method is used, whereby the HumanID is formed from the IP address.
 
   :::
 
@@ -161,6 +192,9 @@ The `fallback` object configures the behavior of the DNS server in case of failu
 
   **Example:** `2s`
 
+[profile-id]:  /private-dns/solving-problems/automatic-devices/#dns-server-id
+[device-type]: /private-dns/solving-problems/automatic-devices/#device-type
+
 ## `debug` {#debug}
 
 The `debug` object configures the debugging features. It has the following properties:
diff --git a/docs/private-dns/connect-devices/mobile-and-desktop/linux.md b/docs/private-dns/connect-devices/mobile-and-desktop/linux.md
index 9144c3810..e0e159d83 100644
--- a/docs/private-dns/connect-devices/mobile-and-desktop/linux.md
+++ b/docs/private-dns/connect-devices/mobile-and-desktop/linux.md
@@ -10,12 +10,20 @@ To connect a Linux device to AdGuard DNS, first add it to *Dashboard*:
 1. Name the device.
     ![Connecting device *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/choose_linux.png)
 
-## Use AdGuard DNS Client
+## Use AdGuard DNS CLI
 
-AdGuard DNS Client is a cross-platform console utility that allows you to use encrypted DNS protocols to access AdGuard DNS.
+AdGuard DNS CLI is a cross-platform console utility that allows you to use encrypted DNS protocols to access AdGuard DNS.
 
 You can learn more about this in the [related article](/dns-client/overview/).
 
+:::note
+
+You can [use AdGuard DNS CLI for automatic device connection][agdnscli-autodevice].
+
+:::
+
+[agdnscli-autodevice]: /dns-client/configuration.md#dns-upstream
+
 ## Use AdGuard VPN CLI
 
 You can set up Private AdGuard DNS using the AdGuard VPN CLI (command-line interface). To get started with AdGuard VPN CLI, you’ll need to use Terminal.
diff --git a/docs/private-dns/connect-devices/other-options/automatic-connection.md b/docs/private-dns/connect-devices/other-options/automatic-connection.md
index f196f3cdf..36886d2a8 100644
--- a/docs/private-dns/connect-devices/other-options/automatic-connection.md
+++ b/docs/private-dns/connect-devices/other-options/automatic-connection.md
@@ -18,6 +18,14 @@ You can create a connection link and use it in the device settings. Your device
 
 Now you can automatically connect your device to the server by creating a special address that includes the device name, device type, and current server ID. Let’s explore what these addresses look like and the rules for creating them.
 
+:::note
+
+You can [use AdGuard DNS CLI for automatic device connection][agdnscli-autodevice].
+
+:::
+
+[agdnscli-autodevice]: /dns-client/configuration.md#dns-upstream
+
 ### Examples of automatic connection addresses
 
 - `tls://adr-{Your_Server_ID}-AdGuard-Test-Device.d.adguard-dns.com` — this will automatically create an `Android` device with the `DNS-over-TLS` protocol named `AdGuard Test Device`