Use this guide to set up and manage a Wallet-as-a-Service (Palisade) organization if you have the Owner or Administrator role.
Owner vs. Administrator
Owners and administrators share nearly identical permissions. The key difference: only owners can update organization-level settings. See User roles and permissions for the full permission matrix.
Use the table below to find the guide for each administrative task.
| Task | Guide |
|---|---|
| Accept your invitation, sign in, and plan your org structure | Initial setup |
| Invite, block, reset, and manage users | Manage users and roles |
| Configure SSO with an identity provider | Configure single sign-on |
| Approve, block, and manage devices | Manage devices |
| Create quorums, reshare and restructure keys | Manage MPC quorums |
| Create vaults and wallets, configure wallet settings | Configure wallets and vaults |
| Design and apply transaction policies | Configure transaction policies |
| Register counterparties and blockchain addresses | Manage counterparties and addresses |
| Set up approval groups for governance | Configure approval flows |
| Create and scope API credentials | Manage API credentials |
| Set up webhook notifications | Configure webhooks |
| Automate fund consolidation with sweeps | Configure asset sweeping |
| Freeze and unfreeze transactions for compliance | Configure transaction freeze controls |
| Create backup and recovery kits for wallet keys | Configure backup and recovery |
| Stream audit logs to AWS Firehose | Configure audit logging |
Make sure you have:
- An invitation email from Palisade for an Owner or Administrator account
- At least 2 devices available for MPC key shard distribution (mobile devices running Palisade Mobile, CloudSign instances, or a combination)
- A list of team members you plan to invite, along with their intended roles
Sandbox and production
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 in production.
| Environment | Console URL | API base URL |
|---|---|---|
| Sandbox | https://app.sandbox.palisade.co | https://api.sandbox.palisade.co |
| Production | https://app.palisade.co | https://api.palisade.co |
If you are setting up a new organization, follow these guides in order. Each step builds on the previous one.
- Initial setup — Sign in and plan your organization structure
- Configure single sign-on — Set up SSO before inviting users (if applicable)
- Manage users and roles — Invite your team
- Manage devices — Approve devices for MPC signing
- Configure backup and recovery — Set up AWS infrastructure for key backups before creating quorums
- Manage MPC quorums — Create signing quorums and assign backup kits
- Configure wallets and vaults — Create vaults and wallets
- Configure transaction freeze controls — Configure wallet-level freeze behavior before enabling sends
- Configure transaction policies — Define allowed transactions
- Manage counterparties and addresses — Register external destinations
- Configure approval flows — Add governance and human oversight
- Manage API credentials — Set up programmatic access (if needed)
- Configure webhooks — Receive real-time event notifications
- Configure asset sweeping — Automate fund consolidation (if needed)
- Configure audit logging — Stream organization activity to AWS Firehose for compliance