# Adding a device

## Install the mobile app

Wallet-as-a-Service Mobile is available on iOS and requires iOS 18 or later. There are separate apps for sandbox and production. Use the sandbox app to try out or test the platform; use the production app for live operations. Install the app that matches the console you use.

|  | Sandbox | Production |
|  --- | --- | --- |
| **Console** | `app.sandbox.palisade.co` | `app.palisade.co` |
| **Where to get the app** | Apple TestFlight: [testflight.apple.com/join/RazUJScm](https://testflight.apple.com/join/RazUJScm) | App Store: [apps.apple.com/app/id6467522678](https://apps.apple.com/app/id6467522678) |


The apps appear as **Palisade Mobile (sandbox)** in TestFlight and **Palisade Mobile** on the App Store. On your home screen the icons are labelled **Palisade [S]** (sandbox) and **Palisade** (production).

Sandbox and production apps are not interchangeable
The sandbox app connects only to the sandbox console, and the production app connects only to the production console. Don't install the sandbox app to use with production, or the production app to use with sandbox.

### Sandbox app (TestFlight)

1. Install the free **TestFlight** app from the App Store, if you don't already have it.
2. On your iPhone, open [https://testflight.apple.com/join/RazUJScm](https://testflight.apple.com/join/RazUJScm).
3. TestFlight opens and offers **Install**. Tap it.
4. Open Wallet-as-a-Service Mobile (sandbox) and [pair the device](#mobile).


TestFlight delivers updates to the sandbox app automatically. If TestFlight reports that the beta is full or the link is no longer valid, contact the Wallet-as-a-Service team.

### Production app (App Store)

1. On your iPhone, open [https://apps.apple.com/app/id6467522678](https://apps.apple.com/app/id6467522678), or search the App Store for the app.
2. Tap **Get** to install the app.
3. Open Wallet-as-a-Service Mobile and [pair the device](#mobile).


## Add a new device

1. Navigate to the ‘Devices’ section in the Wallet-as-a-Service console and click ‘Add a new device’
2. Select a device type (Mobile or Cloud)
3. Enter a name for the device
This name should help identify the device easily.
4. Click ‘Save and continue’


## Pair a new device

By default, the status of new devices will be ‘Unpaired’, indicating that they are not initialised or available for use.

Here is how to pair a device:

### Mobile

1. When a mobile device is added, a QR code will be displayed
2. Open the Wallet-as-a-Service mobile app and scan the QR code. If you haven't installed the app yet, see [Install the mobile app](#install-the-mobile-app).
3. The device in the Wallet-as-a-Service console will move from ‘Unpaired’ state to ‘Waiting for approval’ state. This indicates that the device has been initialized but is not yet ready to use.
4. An admin user will be prompted to ‘approve’ the device pairing
5. The device will then move to ‘Paired’ state and will be ready to use


### CloudSign

1. When a CloudSign device is added, a ‘pairing key’ will be displayed
Similarly to a QR code, the pairing key contains one-time authentication credentials.
2. [Run the CloudSign node](/products/wallet/user-interface/devices/set-up-and-run-cloudsign) and enter the pairing key
3. The device in the Wallet-as-a-Service console will move from ‘Unpaired’ state to ‘Waiting for approval’ state. This indicates that the device has been initialized but is not yet ready to use.
4. An admin user will be prompted to ‘approve’ the device pairing
5. The device will then move to ‘Paired’ state and will be ready to use


## Device settings

Users can access device settings by clicking on the device name.

### View a device

All organization devices will be listed in a table on the Devices page.

Devices belonging to a single user can be viewed from their user profile page.

### Disable a device

Once devices are paired, a ‘disable’ button will appear. Disabling a device prevents the device from being used for approvals or signings.

Only admin users can re-enable a device.

### Delete a device

A device can be deleted from the device page, provided it is not being used as part of an MPC quorum or approval group.

## External devices

### Overview

External devices are devices added by another organization and shared with you.

**Example**: ‘Company A’ may be split into three different entities with separate Wallet-as-a-Service accounts: Company A Australia, Company A UK and Company A USA. If each entity created a device, Company A Australia and Company A UK could share their devices with Company A USA. Company A USA would then be able to create an MPC quorum with their two external devices and one internal device.

### Why are devices shared?

The benefit of sharing devices is that no single entity would have control of all the devices, and therefore, all of the wallet key shards. This minimizes the likelihood of one person accessing all devices in an MPC quorum and using them to authorise transactions.

### Share devices

To enable devices to be shared, both the recipient and sharing organizations need to complete the following steps:

1. Recipient organization - provide their organization name and 36-digit ID to the sharing organization(s). This information can be viewed and copied from Settings → Organization → Details in the Wallet-as-a-Service console.
2. Sharing organization - navigate to the device they want to share and click ‘Share’
3. Sharing organization - enter the recipient organization’s name and ID
4. The shared device will then appear in the recipient organization’s ‘external devices’ tab