Credential Management

Credential management is the process of creating, storing, using, updating, and retiring the credentials used to access accounts and systems. It covers both the login details and the decisions around them, including who can use them and when access should end.

A store may have one account used by support staff, an operations contractor, and the owner. Each needs access for a different reason. Passing around the owner's password gives them a way in, but leaves important questions unanswered. Who can change the login settings? Who receives recovery messages? What happens when the contractor leaves?

What Counts as a Login Credential?

A username identifies an account. A password helps prove that the person signing in is allowed to use it. Depending on the service, access may also involve:

  • Passkeys: Use cryptographic keys to verify a login without sending a reusable password.
  • Authenticator setup secrets: Allow an authenticator to generate verification codes. The setup secret can produce future codes, so it needs more careful handling than a single code.
  • Backup codes: Help the owner regain access when the usual verification method is unavailable.
  • API keys and access tokens: Allow software to connect to an account or service with the permissions it has been given.

Each item needs an owner and a purpose. A backup code belongs in the recovery process. An API key should be tied to a known application, so the team knows what will stop working if it is replaced.

How Is Credential Management Different from Password Management?

Password management handles one part of the job. A password manager can generate a strong password and store it safely. The team still needs to decide who may use it, who controls recovery, and what to do when someone leaves.

Other processes handle what happens around that login:

ProcessWhat It Handles
Credential ManagementThe Credentials, Their Owners, and How They Are Used or Replaced
Password ManagementGenerating, Saving, and Retrieving Passwords
Session ManagementKeeping a Login Active and Ending It
Access ManagementDeciding Which Resources and Actions a User Can Access

For example, a browser may keep a store account open through a saved session token. A teammate who uses that session can access the account without entering its password. The store's permissions then determine what that person can do.

This is why session management belongs in an access review. Changing a password may leave existing sessions active, so check those separately.

How Does Credential Management Work?

Start by finding out how people and tools reach the account. Then manage each credential from setup through removal.

1. Record Who Is Responsible

Keep a record of the account owner, the person responsible for login settings, and the people or tools with access. Include the recovery email and phone number.

With multi-account management, make a separate entry for each client or business account. Someone handling a reset should be able to find the responsible person without searching old messages.

The record can point to a password manager entry. It does not need to contain the password or backup codes itself.

2. Choose How People Will Sign In

Use staff accounts or delegated access where available. Each person can sign in with their own credentials, and the owner can remove that person's access later.

If a shared business login is needed, generate a unique password and save it in a password manager. Set up additional verification and recovery at the same time. Waiting until someone loses their phone makes recovery much harder.

3. Separate Using Credentials from Managing Them

An employee may need to use an account without viewing its saved password or changing its verification method. Check those permissions when assigning access.

Also check whether the person can export credentials, share a saved item, or invite someone else. Otherwise, access intended for one employee may spread beyond the people the owner approved.

4. Replace Credentials When Needed

Change exposed credentials promptly. Also review shared credentials when a project ends or someone who knew them leaves.

For everyday user passwords, NIST guidance advises against mandatory periodic changes without evidence of compromise. Focus on actual exposure rather than changing a strong password just because another month has passed.

For a planned API key replacement, find the tools that use it first. Update their connections, test them, and revoke the old key. This prevents a routine change from silently breaking an order sync or reporting job.

5. Remove Credentials That Are No Longer Needed

When an integration is retired, revoke its key at the service that issued it. Deleting the key from a local file leaves it valid at the service.

When removing an old verification method, check that the remaining owner can still sign in. A company account should not depend on a former employee's phone.

A Credential Management Example for a Store Team

In the store example, support needs order information and the contractor needs to update listings. Neither task requires control of the owner's recovery email.

The owner first checks whether staff logins cover both jobs. If they do, each person receives their own access. There is no need to pass around the main account password.

If an approved task requires a shared browser profile, the owner can assign that environment to the person doing the work. Permission to use it should be considered separately from permission to view saved passwords or change login settings.

In MoreLogin, team roles and permissions help separate access to assigned profiles from management functions. The owner can also use password protection settings to prevent selected roles from viewing passwords saved in browser profiles.

For accounts using Passkey hosting and management, keep management permission with the people responsible for login changes. Someone who uses a configured Passkey does not necessarily need to manage it.

The owner then tests the setup. Support should be able to open the required order details. The contractor should be able to update listings. Recovery and payment settings should remain outside their assigned work.

Hiding the password does not establish those limits inside the store. Use the platform's permissions and applicable browser controls to restrict what each person can do after login.

What Should Change When a Teammate Leaves?

Use the account record to check what the person could access. Work through each route:

  1. Remove assigned access. Check platform membership and browser profile permissions.
  2. End remaining sessions. Review linked devices and active logins.
  3. Review credentials and connections. Replace shared or exposed secrets and revoke connections that are no longer needed.
  4. Check recovery. Remove former staff from recovery contacts and registered verification methods. Replace any backup codes they could still use and confirm that the old codes no longer work.
  5. Test the handoff. Confirm that the remaining owner can sign in and that required business tools still work.

Assign the handoff to a named person and record the changes. The next manager should be able to see what was removed and what was tested.

Credential Management FAQ

Can someone access an account without knowing its password?

Yes. Delegated access, a Passkey, or an existing session may let them in. Check which methods the person can use when deciding whether their access has ended.

Are cookies and tokens login credentials?

Some can grant account access. A cookie may contain a session token, but it may also store a language preference. Protect values that grant access and review them when ending a person's login sessions.

Does changing a password end every active session?

Some platforms do this automatically. Others require you to sign out individual devices or revoke sessions separately. Check the account's active sessions instead of assuming that a password change ended them all.

Who should control account recovery methods?

An authorized business owner should be responsible, with a documented backup process. Recovery should remain available if one employee is absent or leaves. Avoid relying on a personal email address or phone that the business cannot maintain access to.

Start building with MoreLogin

Explore the API reference, automate from the command line, connect MCP-compatible tools, or create reusable RPA workflows.