After navigating to the settings menu, select the System Preferences tab.

In MPC-Driven mode, admin users on the MPC can control many aspects of the Custody Infrastructure system from the System Preferences menu. In Cold-Driven mode, the menu simply lets you know if you are on the most recent version.

For an in-depth explanation of the differences between Cold- and MPC-Driven modes, see Cold-driven vs. MPC-driven Modes.

If you are in Cold-driven mode, accessing MPC System Preferences via the desktop application will show the above message if your MPC software is up-to-date. Otherwise, you will be presented with a means to update your software.

In MPC-Driven mode, admin users can control the following settings directly from the System Preferences area:

Select whether your organization will use Internal AML or Chainalysis for transaction risk assessment.

Activating either AML options requires at least one user be assigned to a role that includes Compliance management permissions. See Roles for details about Compliance management permissions.

For more information about how AML checks operate on the Custody Infrastructure platform, see Anti-Money Laundering.

Running the collector or interacting with an exchange ensures blockchain fees against your account. The options here let you limit how much you allow to be spent per week on collector fees and who can interact with your collectors or exchanges.

Adjust the fee limit by typing a value directly into the Fee Limit box.

Click Edit next to Allowed Users to give permissions to specific users. The user selection menu (pictured below) only allows you to select users individually; user groups cannot be used as a basis for selection.

The transaction approval timeout setting dictates how long a transaction can sit on the Custody Infrastructure system without approvals. If it fails to be approved in the designated timeframe, the transaction is automatically deleted and must be recreated.

Adjust the transaction timeout by typing a value directly into the Timeout box. The setting is in minutes and the default is 300, or five hours.

Keep in mind that the required fees for successfully confirming a transaction are dynamic; the longer you wait between creation and final approval, the greater the chance that fee requirements will have changed and the transaction will become stuck in the mempool.

Conversely, the less time you allow for approving transactions, the more likely an approver will not see the transaction within the window.

Click here to see how many blocks deep a transaction needs to be on a given blockchain for the Custody Infrastructure system to consider it "confirmed". This list is just for your information. The thresholds shown cannot be adjusted.

The Backup indicator lets you know if you have a two-Cold-Vault backup process in place, and, if so, when the most recent backup was performed.

Toggle this on to subject Metamask transactions to the same approval process as any other transaction.