Set up your organization

Ripple creates your organization on the Ripple Custody (Wallet) platform during onboarding. After setup is complete, your organization's first owner receives an invitation email with a link to activate their account. This page walks you through your first sign-in, the decisions to make before you invite your team, and the order in which to configure each part of the platform.

This page is for users with the Owner or Administrator role. If you want to evaluate the platform quickly by sending a first transaction in sandbox, follow the console quickstart instead.

Make sure you have:

• An invitation email from Ripple for an Owner or Administrator account
• A mobile device with an authenticator app (for example, Google Authenticator or Authy) for two-factor authentication (2FA)
• At least 2 devices available for MPC key shard distribution (mobile devices running Ripple Custody (Wallet) Mobile, CloudSign instances, or a combination)
• A list of team members you plan to invite, along with their intended roles

Ripple provides sandbox access during onboarding so you can configure and test the platform before going live. Complete your setup in sandbox first, then repeat it in production.

1. Open the invitation email from Ripple.
2. Select the activation link.
3. Follow the prompts to set your password and configure two-factor authentication (2FA).

1. Go to the Ripple Custody (Wallet) console URL provided during onboarding.
2. On the Enter Your Organization page, enter your organization name, then select Continue.
3. On the Welcome page, enter your email address and password, then select Continue.
4. On the Verify Your Identity page, open your authenticator app, enter the 2FA code, then select Continue.

Ripple Custody (Wallet) supports two authentication methods. An owner in your organization configures which method is available.

Username and password is the default authentication method. Sign in with the credentials you created during account activation.

If your organization has configured SSO with a third-party identity provider (such as Google, Okta, or PingFederate), your organization's login page redirects you to your identity provider after you enter your organization name. Authenticate through your provider to complete sign-in.

After you sign in, the console displays the following main sections in the sidebar:

• Home — View a summary of your organization's activity, including asset totals, vault and wallet counts, address book entries, and pending notifications.
• Vaults — Create and manage vaults and the wallets within them.
• Transactions — View and search transactions across all your wallets.
• Address book — Manage counterparties and their blockchain addresses (tabs: Counterparties, Addresses).
• Devices — Add and manage mobile and CloudSign devices for MPC signing (tabs: Internal, External).
• Controls — Configure approval groups (tab: Approval groups) and MPC quorums (tab: MPC Quorums).
• Connections — Open WalletConnect connections to external dapps.
• Notifications — Open the notifications panel to view pending approval requests (tab: Approvals).
• Settings — Access your account and organization management, including Security, User management, API credentials, Webhooks, Backup & Recovery, Workflows (sweeps), Audit logs, Integrations (travel rule and AML providers), and Registry (assets and blockchains).

Before you invite users or create wallets, decide on these key areas.

Ripple Custody (Wallet) supports two authentication methods: username and password (the default) and single sign-on (SSO) with a third-party identity provider.

Decide which roles your team members need. Ripple Custody (Wallet) provides six roles:

See User roles and permissions for a detailed breakdown of what each role can do.

At minimum, most organizations need:

• At least 2 owners or administrators for redundancy
• At least 1 proposer to initiate transactions
• At least 2 approvers for multi-party approval

Plan how you want to distribute MPC key shards across devices. Consider:

• How many devices hold key shards (more devices = higher resilience)
• How many devices must sign each transaction (higher threshold = stronger security)
• Who controls each device (distribute across team members for separation of duties)
• Device types — mobile devices for manual review, CloudSign for automated signing, or a mix

Decide which operations require human approval before they take effect:

• Transactions
• Address book entries
• Policy rule changes
• API credential creation
• User invitations
• Device registration

A fintech company uses Ripple Custody (Wallet) to manage institutional ETH and XRP custody. Their team has 6 people:

Their decisions:

• Authentication — SSO with Okta, configured before sending invitations.
• Quorum design — one 3-of-5 Cloud quorum using CloudSign instances for automated signing. The higher threshold balances security with availability.
• Vault structure — two vaults: "Hot Wallet Operations" for daily trading and "Cold Storage" for reserve holdings.
• Approval structure — transaction approval group with Lisa and Tom as approvers, threshold of 1. Address and policy approvals require both (threshold of 2) since these changes are less frequent but higher risk.
• Policies — per-transaction limit of 50 ETH on hot wallets, rolling 24-hour limit of 500 ETH. Cold storage has lower limits and restricted destinations.
• Freeze controls — automatic freeze enabled on cold storage wallets for compliance review of every deposit.

This gives them separation of duties (traders propose, compliance approves), automated signing (CloudSign), and layered controls (policies + approvals + freeze).

After you plan your organization structure, configure each component in this order. Each step builds on the previous one.

After setup, prepare for incidents: Disaster recovery describes how to restore a node database or recover wallets.