diff --git a/content/contracts/5.x/access-control.mdx b/content/contracts/5.x/access-control.mdx
index 064fea3a..89d8fe69 100644
--- a/content/contracts/5.x/access-control.mdx
+++ b/content/contracts/5.x/access-control.mdx
@@ -110,8 +110,7 @@ This is the issue the [`TimelockController`](/contracts/5.x/api/governance#Timel
 The [`TimelockController`](/contracts/5.x/api/governance#TimelockController) is a proxy that is governed by proposers and executors. When set as the owner/admin/controller of a smart contract, it ensures that whichever maintenance operation is ordered by the proposers is subject to a delay. This delay protects the users of the smart contract by giving them time to review the maintenance operation and exit the system if they consider it is in their best interest to do so.
 
 ### Using `TimelockController`
-
-By default, the address that deployed the [`TimelockController`](/contracts/5.x/api/governance#TimelockController) gets administration privileges over the timelock. This role grants the right to assign proposers, executors, and other administrators.
+The address that deploys the [`TimelockController`](/contracts/5.x/api/governance#TimelockController) does not automatically receive administration privileges over the timelock. In order for the deployer address to acquire administrative privileges, you must pass the deployer address as the `admin` argument in the constructor. This role grants the right to assign proposers, executors, and other administrators.
 
 The first step in configuring the [`TimelockController`](/contracts/5.x/api/governance#TimelockController) is to assign at least one proposer and one executor. These can be assigned during construction or later by anyone with the administrator role. These roles are not exclusive, meaning an account can have both roles.