Skip to main content
During onboarding, clients often need to share sensitive details such as admin passwords, API keys, or service account logins. Credential handoff is a purpose-built task that encrypts what the client submits and lets your team retrieve it once. This page explains how it works and links to the step-by-step guides.

​
Find the guide you need

​
How it works

1

The client submits

The client fills in Username, Password, API Key, and Notes (Single mode), or pastes text and attaches a file (Bulk mode). A confirmation reminds them they cannot edit the submission afterward.
2

MSPortal encrypts it

The details are encrypted with AES-256-GCM using a unique random key. The key is stored in a separate secrets vault, apart from the encrypted data.
3

You reveal it once

On the credential task, you select Reveal Credentials and confirm Reveal & Delete. The details show for 5 minutes so you can copy them.
4

The stored copy is deleted

When you reveal the credentials, MSPortal deletes the encrypted data and its key. Nobody can retrieve the submission again.

​
What protects the data

​
Credential statuses

​
What to tell your clients

You can share this with clients to build trust. “Your credentials are encrypted the moment you submit them. The encryption key is stored separately from the encrypted data. Our team can view them one time, and then the stored copy is deleted. If we have not retrieved them after 30 days, they expire and you will need to submit them again.”

​
Troubleshooting

​
Frequently asked questions

No. They can be revealed once. If you need them again, create a new credential handoff task.
The submission shows Expired and cannot be retrieved. Create a new handoff task and ask the client to resubmit.
No. If they made a mistake, create a new handoff task for them.
In a secrets vault that is separate from the database that holds the encrypted data. Each submission has its own key.
AES-256-GCM, which protects both the privacy and the integrity of the data.