Skip to main content
Policy requests are how Fortary manages changes to your organization’s security policies — such as adding or removing whitelisted addresses. Every policy change goes through the same structured approval workflow as transactions, ensuring that no policy is modified without the proper level of review.

​
Example of a Policy Request

ActionRequest Type
Add a new whitelisted addressInsert Whitelisted Address
Remove an existing whitelisted addressDelete Whitelisted Address

​
Policy Request Lifecycle

Created → Pending Approval → Approved → Completed
                          ↘ Rejected (at any stage)
StatusMeaning
Pending ApprovalAwaiting the required number of approvals
ApprovedApproval threshold met; ready to be completed
CompletedThe policy change has been applied
RejectedThe request was rejected and will not take effect

​
Who Can Create Policy Requests

Users with the Initiator role on a vault can create policy requests for that vault. Policy requests are vault-scoped — access to one vault does not grant the ability to create requests for other vaults.

​
Who Can Approve Policy Requests

Users with the Approver role review and approve or reject policy requests. The number of approvals required before a request can be completed is set by your organization’s policy configuration and is visible on each request as Approvals X / Y.

​
Viewing Policy Requests

Navigate to Requests → Policies to see all policy requests for your entity.
ColumnDescription
StatusCurrent state of the request
DateWhen the request was created
TypeThe type of policy change
VaultThe vault this request applies to
InitiatorWho created the request
ApprovalsApproval progress (e.g., “1 / 2”)
Use the Status and Vault filters to narrow the list. Filtered views are reflected in the page URL and can be bookmarked or shared.

​
Approving a Policy Request

  1. Click a request row to open the detail view
  2. Review the policy change — for address requests this includes the address, name, network, vault, and whether it is classified as internal or external
  3. Click Approve
Approving a policy request requires a cryptographic signature tied to your approver credentials, just like approving a transaction. Each approval is logged in the request record. If the approval threshold has not been met after your approval, the request remains in Pending Approval until additional approvers act.

​
Rejecting a Policy Request

Click Reject on the request detail page. Rejections are final — the initiator must submit a new request if the change is still needed.

​
Sharing a Policy Request

Policy request detail pages have a direct URL that can be shared with other team members for review. If the recipient belongs to a different entity, they will see an access notice.