Manage Your Account

Your profile belongs to you, not to an organization. A change applies in every organization you belong to. This guide covers the four things you can change about your account: the profile, the password, the linked sign-in providers, and the account itself.

Before you start 🔗

• You need the View Profile permission to open the profile. The default user role holds it.
• Changing your password needs Reset Password. Deleting the account needs Delete Account. The default user role holds both.
• Layer5 Cloud signs you in through an identity service. Password changes and account deletion need a live browser sign-in. A script that holds only an API token cannot do either.
• Changing a password or linking a provider is a privileged action. If your sign-in is older than the privileged-session window, Layer5 Cloud asks you to sign in again first. The window is 24 hours on hosted Layer5 Cloud and 15 minutes by default in the self-hosted chart.
• A user’s profile can also be edited by an administrator who holds Update User Profile in an organization you share with them. Only a Provider Admin can change another user’s email address.

Edit your profile 🔗

The profile form saves itself. About one second after you stop typing, Layer5 Cloud saves the change and confirms it with a short message. There is no Save button, and edits made during a save are queued, not lost.

Your avatar, tagline, and social links appear on your public profile.

Change your email address 🔗

Changing the email address changes the identifier you sign in with. Layer5 Cloud marks the new address as unverified and sends it a verification message. The confirmation reads “Profile updated. Please check your new email address to verify it.” Verify the new address before you rely on it. If the verification message cannot be sent, the change still completes.

Layer5 Cloud writes the change to the identity service first and to your profile second, so a rejected address never leaves the two out of step.

Change your password 🔗

Use the Reset Password control on the profile. Enter the new password twice. The two entries must match, or the form reports “Your new passwords do not match”.

The identity service enforces the password policy:

• At least 8 characters.
• Not a password found in known breaches.
• Not too similar to your email address.

A strength bar (Very weak to Strong) shows how guessable the password is. It is advice only and does not block you; the policy above does. A rejected password returns the identity service’s reason. A successful change shows “Password updated”.

Changing your password does not end your other sessions or revoke your API tokens. To cut off a device or script, end the session or revoke the token yourself with Review and Sign Out Sessions and Create and Use an API Token.

If you forgot your password, use the recovery flow from the sign-in page instead. It emails a one-time code and link that stay valid for 30 days.

Link or unlink a sign-in provider 🔗

Link GitHub or Google to sign in with whichever you prefer. Either method opens the same account, with the same organizations, designs, and roles. GitHub and Google are the only supported providers.

The profile lists a Link option for each provider you have not linked and an Unlink option for each provider you have linked. The provider you used to create the account appears in neither list: you cannot unlink it, and it is already linked.

Linking sends you to the provider to approve access, then returns you to Layer5 Cloud. Layer5 Cloud asks GitHub for your profile and email address and Google for your email and profile. Unlinking removes the provider from your account. Your password and the other linked provider keep working.

A provider account can be linked to one Layer5 Cloud account only. Linking depends on the provider reporting a verified email address. For how Layer5 Cloud resolves sign-ins that share an email address, read Account Consolidation and the Account Linking rules.

Delete your account 🔗

Deletion is permanent. Layer5 Cloud asks you to confirm, and then does not offer recovery.

What deletion does:

1. Hands any credential you hold on behalf of an organization to that organization’s successor, so the organization keeps working. The successor is the organization’s owner, or else its longest-standing Organization Admin.
2. Marks your account as deleted and removes your memberships in every organization and team, which removes your roles with them.
3. Records the deletion in the audit trail.
4. Removes your sign-in identity, including linked GitHub and Google sign-in, and signs you out.

What deletion leaves behind:

• Published content, such as items you published to the catalog, stays public.
• Organizations you own continue to exist. Deleting your account does not delete or transfer them.
• The audit trail keeps its entries.

Re-registering with the same email address does not restore the old account or re-link a provider.

When deletion is refused 🔗

Layer5 Cloud refuses the deletion, and changes nothing, when you are the only owner or Organization Admin of an organization that holds credentials designated to it. The message begins “Refusing to delete your account” and names the organization. Without a successor, those credentials would be orphaned.

Resolve it, then retry:

• Promote another member of that organization to Organization Admin. An organization’s ownership cannot be transferred, so a second Organization Admin is the way to give it a successor.
• Or release the credentials from the organization, or delete them.

See also 🔗

• Users explains accounts, memberships, and sign-in methods.
• Set Notification Preferences controls the email you receive.
• Security covers sessions and API tokens.

Related Reading

• Your Account
• Recognize Members with Badges
• Account Consolidation
• Bring Your Own Mail Server
• Child Organizations
• Identity and Security