Share a password with a little less exposure.
First consider whether you can invite someone to their own account instead of sharing yours. Separate accounts make access easier to revoke and keep responsibility clear. When a temporary secret really must be shared, an encrypted note can keep it out of an ordinary message history.
Prepare the handoff
- Open DRK Note. Include only what the recipient needs.
- Choose an expiry that gives them enough time. Add a strong note password if the link alone should not grant access.
- Create the note and send the complete link to the intended recipient. If you set a password, communicate it through a separate trusted channel.
- For account credentials, rotate or revoke the shared credential when the task ends. Deleting a note does not revoke the underlying account access.
Treat the whole link as sensitive
The part after the # sign contains key material. Keep the link out of public tickets, screenshots and shared analytics. A password adds a requirement; it does not make forwarding the complete link harmless.
This workflow relies on a trustworthy browser, device and delivered application. Encryption cannot stop an intended recipient from copying what they read. For a fragile handoff, an ordinary expiry may be more practical than deleting the note after its first retrieval.
Review the privacy boundaries of DRK services when deciding whether it fits the material.