Share One Salesforce Account With Multiple Users

By Kalpesh Mahida · Updated August 29, 2026

Plenty of teams sign in to one Salesforce account on purpose: a shared sandbox, an operations service account, a login a couple of admins both use. Since July 2026, phishing-resistant MFA made that harder, because the accepted factors bind to one device. This guide covers when sharing one Salesforce account is allowed, and how multiple users can sign in to it without handing a password around.

Is sharing one Salesforce account allowed?

Salesforce is built around named users, and its licensing expects each named user to have their own login. Do not share a named-user license across distinct people to dodge buying seats. That is a licensing problem, not a security one. What is legitimate is a genuine service account: one identity that is not a specific person, used by a small team for a shared task. Share those, and keep individual humans on their own accounts.

What the 2026 MFA change means for a shared account

For privileged users, a one-time code from an authenticator app or SMS no longer clears the bar. The account needs a phishing-resistant factor: a passkey, a device authenticator like Windows Hello, or a hardware key. All bind to one device, which is exactly what makes a shared account awkward. The fix is to store the factor where the team can reach it, not on one person device.

How multiple users sign in to one Salesforce account

The realistic options, briefly (the full guide covers each with its tradeoffs):

• Give each person their own seat and passkey. Clean, but you pay per seat.
• Temporary Verification Code from Salesforce. Fine for rare, short-lived access, tedious for regular use.
• A shared password manager that stores the passkey. Good if you already run one across the team.
• A free single-purpose tool like Coauth that shares one login without a suite or a per-seat cost.

Step by step with Coauth

1. Install Coauth and secure your vault with your device passkey.
2. Save the shared account login, or register a passkey for it, in Coauth.
3. Create a team and share the login into it.
4. Invite the people who need it. The login appears in their vault, decrypted only on their device.
5. Remove anyone who leaves. The team key rotates so their copy stops working.

When to give people their own accounts instead

If each person needs their own audit trail, or you are under rules that require named users, do not share. Buy seats and let each enroll a passkey. Sharing one account always trades some accountability for convenience. Make that trade only for accounts that are genuinely shared.

Frequently asked questions