Colour theme
Book a consultation

Replacing shared logins at work

Replace shared staff logins with named accounts, delegated access or shared mailboxes, and manage exceptions when software only supports one login.

Keys hanging from a door lock in a black-and-white photograph.

Your team shares one login to the accounting system. It lets everyone finish their work, but a change to supplier banking details appears under the same username whether the bookkeeper, a manager or someone outside the business made it.

A shared login makes access harder to trace and remove. Start by checking whether the software supports named users, roles or delegated access you haven’t configured yet.

Identify which logins people share

List the systems where staff use someone else’s credentials or a common username. Include finance, customer records, website administration, cloud storage and specialist software. Ask the people doing the work which accounts they use; a subscription list may miss older tools.

For each login, record what it controls, who can use it, who owns it and what would stop working if the password changed. Keep the password itself in the business password manager.

Separate staff logins from accounts used by software. A backup process or integration needs its own review before you change credentials. Label its purpose and dependencies so it isn’t disabled during a staff-access cleanup.

Understand the limits of a shared identity

When several people use one identity, an application may record their activity under that account. Even if it records device or network details, those clues may not show who made a particular change.

The Cyber Centre’s baseline controls for small and medium organizations recommend unique individual accounts and minimizing shared accounts to support accountability. Named accounts also let you match permissions to someone’s work and remove their access individually.

A named account can still be compromised, so keep audit logging turned on and check unexpected activity with the person whose account it is.

MFA needs a workable arrangement too. If everyone’s sign-in prompt goes to one person’s phone, staff may start approving requests they didn’t initiate. With named accounts, each person can protect their own sign-in and report unexpected prompts.

Give administrators separate accounts

Prioritize logins that can create users, change security settings or manage payments. Review whether everyone using them needs those permissions.

The Cyber Centre’s administrative-access guidance recommends identifiable administrator accounts, MFA and separate accounts for ordinary work such as email. Give each administrator their own admin account and use it only for tasks that require it.

Don’t use an emergency-access account as the team’s daily login. Have your IT provider document how emergency access is protected, monitored and tested.

Use a shared mailbox without sharing a password

A team address for sales or support can remain shared while staff sign in individually.

Microsoft 365 shared mailboxes are opened from the mailboxes of the people you’ve given access. Microsoft says to block direct sign-in to the shared mailbox account and keep it blocked. Your administrator can assign the reading and sending permissions needed for the team’s work.

Each user needs their own licensed Exchange Online mailbox. Some shared-mailbox storage and compliance features require additional licensing. Confirm the requirements before treating this as a way to remove licences.

Other applications may offer team inboxes, roles or delegation. Ask the vendor which option supports your workflow, audit needs and number of users.

Move one workflow at a time

Start with high-impact accounts and the ones known by former employees. For each system:

  1. Confirm supported user roles, licence costs and required access.
  2. Create named accounts and configure each person’s MFA.
  3. Test a real task with the intended permissions, including any sign-off steps.
  4. Transfer account ownership and recovery arrangements where needed.
  5. Remove the old staff access, then verify that the team can still work.

Check integrations before retiring a login. If software depends on a staff account, ask your IT provider and the vendor about a supported service identity or another authentication method. Don’t simply disable MFA to keep the integration running.

Manage the remaining exceptions

Some equipment or older software only supports one login. Assign an internal owner and document why sharing remains necessary, who’s allowed to use it and when you’ll review a replacement.

Use a business password manager with named users and MFA to restrict access to the credential. The team vault guide covers setting that up. A vault can help control who retrieves it, but it doesn’t make the application’s own activity attributable to each employee. Someone who copied the password may still have it after vault access is removed.

When someone who used it leaves, change any shared credential they could use. Review sessions, recovery methods and other access separately. Test affected workflows after the change and update the credential in any software that depends on it.

Make access reviews part of onboarding, role changes and departures. Give staff a documented way to request access so the next urgent task doesn’t reintroduce a password shared through email.


Featured Image Credit