diff --git a/templates/compose/signoz.yaml b/templates/compose/signoz.yaml
index f4209b01f..6877ef9e5 100644
--- a/templates/compose/signoz.yaml
+++ b/templates/compose/signoz.yaml
@@ -1229,133 +1229,6 @@ services:
                   <continue_if_corrupted>true</continue_if_corrupted>
               </merge_tree_metadata_cache>
           </clickhouse>
-      - type: bind
-        source: ./clickhouse/users.xml
-        target: /etc/clickhouse-server/users.xml
-        content: |
-          <?xml version="1.0"?>
-          <clickhouse>
-              <!-- See also the files in users.d directory where the settings can be overridden. -->
-
-              <!-- Profiles of settings. -->
-              <profiles>
-                  <!-- Default settings. -->
-                  <default>
-                      <!-- Maximum memory usage for processing single query, in bytes. -->
-                      <max_memory_usage>10000000000</max_memory_usage>
-
-                      <!-- How to choose between replicas during distributed query processing.
-                          random - choose random replica from set of replicas with minimum number of errors
-                          nearest_hostname - from set of replicas with minimum number of errors, choose replica
-                            with minimum number of different symbols between replica's hostname and local hostname
-                            (Hamming distance).
-                          in_order - first live replica is chosen in specified order.
-                          first_or_random - if first replica one has higher number of errors, pick a random one from replicas with minimum number of errors.
-                      -->
-                      <load_balancing>random</load_balancing>
-                  </default>
-
-                  <!-- Profile that allows only read queries. -->
-                  <readonly>
-                      <readonly>1</readonly>
-                  </readonly>
-              </profiles>
-
-              <!-- Users and ACL. -->
-              <users>
-                  <!-- If user name was not specified, 'default' user is used. -->
-                  <default>
-                      <!-- See also the files in users.d directory where the password can be overridden.
-
-                          Password could be specified in plaintext or in SHA256 (in hex format).
-
-                          If you want to specify password in plaintext (not recommended), place it in 'password' element.
-                          Example: <password>qwerty</password>.
-                          Password could be empty.
-
-                          If you want to specify SHA256, place it in 'password_sha256_hex' element.
-                          Example: <password_sha256_hex>**PASSWORD HASHED WITH SHA256**</password_sha256_hex>
-                          Restrictions of SHA256: impossibility to connect to ClickHouse using MySQL JS client (as of July 2019).
-
-                          If you want to specify double SHA1, place it in 'password_double_sha1_hex' element.
-                          Example: <password_double_sha1_hex>**PASSWORD HASHED WITH SHA1**</password_double_sha1_hex>
-
-                          If you want to specify a previously defined LDAP server (see 'ldap_servers' in the main config) for authentication,
-                            place its name in 'server' element inside 'ldap' element.
-                          Example: <ldap><server>my_ldap_server</server></ldap>
-
-                          If you want to authenticate the user via Kerberos (assuming Kerberos is enabled, see 'kerberos' in the main config),
-                            place 'kerberos' element instead of 'password' (and similar) elements.
-                          The name part of the canonical principal name of the initiator must match the user name for authentication to succeed.
-                          You can also place 'realm' element inside 'kerberos' element to further restrict authentication to only those requests
-                            whose initiator's realm matches it.
-                          Example: <kerberos />
-                          Example: <kerberos><realm>EXAMPLE.COM</realm></kerberos>
-
-                          How to generate decent password:
-                          Execute: PASSWORD=$(base64 < /dev/urandom | head -c8); echo "$PASSWORD"; echo -n "$PASSWORD" | sha256sum | tr -d '-'
-                          In first line will be password and in second - corresponding SHA256.
-
-                          How to generate double SHA1:
-                          Execute: PASSWORD=$(base64 < /dev/urandom | head -c8); echo "$PASSWORD"; echo -n "$PASSWORD" | sha1sum | tr -d '-' | xxd -r -p | sha1sum | tr -d '-'
-                          In first line will be password and in second - corresponding double SHA1.
-                      -->
-                      <password></password>
-
-                      <!-- List of networks with open access.
-
-                          To open access from everywhere, specify:
-                              <ip>::/0</ip>
-
-                          To open access only from localhost, specify:
-                              <ip>::1</ip>
-                              <ip>127.0.0.1</ip>
-
-                          Each element of list has one of the following forms:
-                          <ip> IP-address or network mask. Examples: 213.180.204.3 or 10.0.0.1/8 or 10.0.0.1/255.255.255.0
-                              2a02:6b8::3 or 2a02:6b8::3/64 or 2a02:6b8::3/ffff:ffff:ffff:ffff::.
-                          <host> Hostname. Example: server01.clickhouse.com.
-                              To check access, DNS query is performed, and all received addresses compared to peer address.
-                          <host_regexp> Regular expression for host names. Example, ^server\d\d-\d\d-\d\.clickhouse\.com$
-                              To check access, DNS PTR query is performed for peer address and then regexp is applied.
-                              Then, for result of PTR query, another DNS query is performed and all received addresses compared to peer address.
-                              Strongly recommended that regexp is ends with $
-                          All results of DNS requests are cached till server restart.
-                      -->
-                      <networks>
-                          <ip>::/0</ip>
-                      </networks>
-
-                      <!-- Settings profile for user. -->
-                      <profile>default</profile>
-
-                      <!-- Quota for user. -->
-                      <quota>default</quota>
-
-                      <!-- User can create other users and grant rights to them. -->
-                      <!-- <access_management>1</access_management> -->
-                  </default>
-              </users>
-
-              <!-- Quotas. -->
-              <quotas>
-                  <!-- Name of quota. -->
-                  <default>
-                      <!-- Limits for time interval. You could specify many intervals with different limits. -->
-                      <interval>
-                          <!-- Length of interval. -->
-                          <duration>3600</duration>
-
-                          <!-- No limits. Just calculate resource usage for time interval. -->
-                          <queries>0</queries>
-                          <errors>0</errors>
-                          <result_rows>0</result_rows>
-                          <read_rows>0</read_rows>
-                          <execution_time>0</execution_time>
-                      </interval>
-                  </default>
-              </quotas>
-          </clickhouse>
       - type: bind
         source: ./clickhouse/custom-function.xml
         target: /etc/clickhouse-server/custom-function.xml