Before sharing a login, decide what the other person needs to see and how you will end their access. A password record may contain more than a password: notes, a TOTP secret, and access to incoming messages can all matter. Review the whole record before granting access.
Use this workflow for a personal PasswordX record and an existing PasswordX recipient. Start by checking whether the external service offers separate accounts or delegated access. When each person can have their own identity at that service, it is easier to remove one person's access without replacing a shared credential.
Define the smallest useful share
Write down the task the other person needs to complete. Then compare that task with everything inside the record. Remove unrelated notes or choose a dedicated record when practical. Do not include your own recovery material merely because it was convenient to store it nearby.
Personal sharing in PasswordX can give a recipient read-only access to a record. Read-only describes their ability to change the shared record. It still lets them read the credentials you provide, and those credentials may allow substantial actions at the external service. A read-only password record does not turn the external account into a read-only account.
Before confirming, check the recipient's identity through a channel you already trust. Similar names and familiar-looking addresses are poor reasons to skip this step. Ask the person to confirm the account they intend to use without asking them to send you their password.
Review attached alias mail
A PasswordX record can have an incoming AliasX address attached. Sharing that record can also give the recipient access to its attached alias messages. Treat the messages as part of the sharing decision, especially if the external service sends sign-in links, verification codes, or password reset messages to that address.
Check whether the alias is dedicated to this one account. If you have used the same address for unrelated registrations, sharing its incoming messages may reveal more than the task requires. Resolve that before sharing. Tell the recipient what messages the record includes so that the scope is understandable to both of you.
Sharing an attached alias does not give the recipient your primary mailbox or every other alias. Equally, the word “password” in the record's title is not a reliable description of all the access it contains. Inspect the attachment and notes rather than relying on the title.
Verify the recipient's actual view
After sharing, ask the recipient to open the intended record in their own account and confirm that it is the right one. They can confirm the service name and task without reading the password back to you or posting screenshots of the secret.
Agree on a clear end condition: the task is finished, the shared subscription ends, or you choose to stop sharing. Keep a simple private note of who has access and why. This makes the later decision about revocation easier, particularly when you share several different records with the same person.
Understand what revoke changes
Revocation closes future access through the permission you remove. Check for any other permission that still gives the recipient access to the same record, such as access through a shared vault. Removing one route should not be treated as proof that every route has disappeared.
Revocation cannot make someone forget a password, erase a screenshot, or retrieve messages they already copied. The same applies to a TOTP secret: a retained copy can generate codes until the protected service replaces or disables that secret.
If you need to end access to the external account itself, change its password there and review its active sessions, recovery methods, and authenticators. Update the retained password record afterward. These are separate actions from removing a share in PasswordX. OWASP's secrets management guidance likewise distinguishes restricting access to a secret from replacing or revoking the credential at the system that accepts it.
Close the loop
After revoking, refresh the sharing view and confirm the intended permission is gone. If the result is unclear, check the current state before repeating the action. Do not use the disappearance of an old browser tab as your only evidence.
Finally, decide whether the external credential needs replacement based on what the recipient could have learned and whether they should retain any access. A useful exit plan covers both the shared record and the account it opens.