The awkward moment of sharing a secret
In ordinary work, there is a moment when someone needs an access detail: a person must enter a service, confirm a configuration, or complete an installation. Pasting it into an email or chat seems quick, but it ties the value to a history that can be forwarded, archived, or left visible long after the work is done.
Confidential Sends changes that moment. You write only the necessary text, choose the recipient, and send a temporary invitation. The recipient does not need to create an account; they receive a simple page and use the method you selected. The delivery stays separate from everyday conversation and can close once its purpose is complete.
Choose how to verify the right person can open it
You can require a six-digit code sent to the destination email, use a direct link, or separate the link and key across two channels. A code adds a check within the delivery channel. A direct link removes steps, but anyone who can open the invitation may try to access it. A separate key requires extra coordination, such as a phone call, and keeps the second part outside email.
The choice should match the risk and the task. A short instruction someone will copy during a call may work with a direct link; a higher-impact credential may deserve a separate key. The feature offers choices, but it cannot determine whether the email truly belongs to the person who requested the information. That verification remains the team's responsibility.
Decide the closing rule before sending
A send can close when the recipient confirms they are done, when they use the copy action, or when the message is displayed. You can also choose whether deletion happens immediately or twenty-four hours after that action. This matters because one person may need to consult a value more than once during setup, while another delivery should disappear as soon as it is read.
If the send does not trigger its closing rule, it expires twenty-four hours after creation. Think about the task before choosing the timing: immediate deletion after display may fit a one-time reading, but frustrate someone who still needs to paste the value into two screens. The behavior should match the real work.
A separate delivery for each person
Each send belongs to one specific recipient. If two people need the same value, separate deliveries keep invitations, expiration, and revocation decisions clear. The list shows whether an invitation is pending, sent, or undeliverable, and whether it remains available so you can act without searching through all email.
If the address was wrong, revoke the send and create a new one. If the value may have been seen, change the secret in its source service as well. Revocation cuts access inside the delivery, but it cannot erase a screenshot, note, or copy someone already saved elsewhere. Security depends on both closing the send and responding afterward.
For one-time text, not for managing secrets
Confidential Sends supports text, not files or collaboration. It is for delivering one piece of information without leaving it in a conversation channel; it does not create a permanent collection or let several people manage the same secret. For personal credentials used every day, AgentticVault provides a different vault. For expiring large-file delivery, Transfers is the appropriate choice.
The feature also does not replace the recipient's identity or an internal policy. The team must review the address, include only what is necessary, and use a separate channel when appropriate. Its value is reducing how long text remains in email and making the access end explicit, not promising control over what happens after someone copies it.