From 4b03145df89155e25e5975e808552f33f9f0e3a7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ernesto=20Garc=C3=ADa?= Date: Thu, 9 Nov 2023 16:27:40 +0000 Subject: [PATCH] Close `access-control.adoc` code block (#4726) --- docs/modules/ROOT/pages/access-control.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/modules/ROOT/pages/access-control.adoc b/docs/modules/ROOT/pages/access-control.adoc index 5b334c2fe9e..544fc9bdf62 100644 --- a/docs/modules/ROOT/pages/access-control.adoc +++ b/docs/modules/ROOT/pages/access-control.adoc @@ -188,6 +188,7 @@ await manager.setTargetFunctionRole( ['0x40c10f19'], // bytes4(keccak256('mint(address,uint256)')) MINTER ); +``` Even though each role has its own list of function permissions, each role member (`address`) has an execution delay that will dictate how long the account should wait to execute a function that requires its role. Delayed operations must have the xref:api:access.adoc#AccessManager-schedule-address-bytes-uint48-[`schedule`] function called on them first in the AccessManager before they can be executed, either by calling to the target function or using the AccessManager's xref:api:access.adoc#AccessManager-execute-address-bytes-[`execute`] function.