Skip to content
Custody Docs Paribu Custody

Admin Quorum

In Paribu Custody, workspace-based features such as workspace settings, user management, and transaction policies are used with the approval of the owners and admins. Each workspace has an “Admin Quorum” community, where users with admin, associate, and owner roles are automatically included. The admin quorum does not allow adding or removing users. Everyone with the relevant role is a member of the admin quorum.

In the workspace, requests requiring approval are forwarded to admin quorum members. Admin quorum members finalize requests by selecting the “approve” or “reject” action via their mobile devices or API.

Admin quorum features are as follows:

  • Users with owner, admin, associate roles, and “active” key shard status are automatically included in the admin quorum.
  • In admin quorum requests, owner approval is always mandatory, in addition to the required number of approvals (threshold) for admin quorum approval.
  • Until the completion of approvals in the relevant threshold, requests for admin quorum approval are automatically rejected upon receiving a “reject” action.
  • If there is an active admin quorum request and the admin quorum threshold is changed before completion, the active request will be processed according to the latest admin quorum threshold.
    • Example:
      • Admin quorum threshold = 4
      • A “Transaction Policy Change” request has been created.
      • The request has been approved by only one admin. It awaits three admin approvals.
      • The admin quorum threshold has been changed to six.
      • The ongoing “Transaction Policy Change” request now awaits five admin quorum approvals instead of three.
  • An ongoing admin quorum request must result in either a “reject” or “approve” action by the admin quorum members. The created admin quorum request cannot be canceled, nor can a different request be created for the same request type.
    • Example: A policy change has been made in a workspace. If the user who made the change cancels the said change, one of the admin quorum members must reject the request. Otherwise, the change will not be canceled. A new policy change cannot be made until the approval process is completed, regardless of the outcome.

Admin Quorum Threshold

Section titled “Admin Quorum Threshold”

The admin quorum threshold determines the number of admin quorum “approvals” needed to finalize requests. This threshold is set to “all” by default for each created workspace. Changing the admin quorum threshold requires admin quorum approval. Accordingly, changing the threshold, which is set to “all” by default, is only possible with the simultaneous approval of all admin quorum users in the workspace.

  • Example: There are 20 users in the admin quorum. Threshold has been set as “5” by the admin quorum. Any action awaiting admin quorum approval will be completed successfully once approved by five admin quorum members.

To change the threshold number:

  • An individual in the admin quorum enters the change using the Update Quorum Threshold button.
  • The change is completed when the threshold number is reached and the owner’s approval is obtained.

Actions Requiring Admin Quorum Approval

Section titled “Actions Requiring Admin Quorum Approval”
  • Adding a user to the workspace
  • Deleting a user from the workspace
  • Changing the admin quorum threshold
  • Changing the admin quorum time lock
  • Allowing transfers to non-whitelisted addresses
  • Adding whitelisted addresses
  • Creating groups
  • Updating groups
  • Deleting groups
  • Updating the Transfer Policy
  • Resetting an API user’s API Key
  • Updating the workspace deposit type
  • Connecting to an AML provider
  • Ending a connection with an AML provider
  • Updating the AML Policy

Admin Quorum Time Lock

Section titled “Admin Quorum Time Lock”

Users can choose the duration it will take for the admin quorum requests to become active after all approvals have been completed. The time lock can be set within a range of 0 to 24 hours. The purpose of this feature is to prevent pending requests from being affected by any setting changes that could impact the workspace, while offering additional control time.

Setting a time lock is an admin quorum request. When there is an admin quorum time lock in the workspace, changing the time limit requires waiting for the currently set time to expire.

  • Example: In a workspace, the admin quorum time lock is to be reduced from three hours to one hour. After this request receives all approvals, there will be a waiting period of three hours for the time lock to drop to one hour.