01
Choose the right account
Before entering a password or approving a provider sign-in, confirm that you are using the MemoID account you actually intend to use. This matters when you have several personal or work accounts.
This guide explains MemoID from the perspective of a real user: what each menu is for, when you should use it, what information you will see, what happens after you confirm an important action, and which details are only relevant to administrators or developers.
After you enter an application, that application decides what you can do inside it—for example whether you are an administrator, editor, viewer or member of a particular team. This distinction is important when an app says you can sign in but cannot use a specific feature.
You do not need to understand OAuth or identity protocols to use MemoID safely. Focus first on who you are signing in as, which application is asking, what information it wants, and whether the activity still looks familiar afterward.
Before entering a password or approving a provider sign-in, confirm that you are using the MemoID account you actually intend to use. This matters when you have several personal or work accounts.
Confirm the application name and destination. If a request appears unexpectedly or you do not recognize the app, cancel it rather than approving first and investigating later.
MemoID shows the categories of identity information an application requests. Read them in plain terms—identity, profile, email or continued connection—before choosing to continue.
After sign-in, use Connected applications, Devices and Security activity to review access over time. Remove connections you no longer need instead of leaving old access active indefinitely.
During sign-in, an application may ask MemoID for specific categories of identity information. The technical names are called scopes, but what matters to most users is what each category allows the application to know or continue doing.
openid
profile
email
offline_access
A phone can change IP address throughout the day. A VPN can show another city. A browser update can change how the device is identified. Compare the time, device, browser, sign-in method and nearby activity together. If several details do not match your own use, end that access and review the account immediately.
Changing a password, disconnecting providers, signing out every device and recovering an account are different actions with different consequences. Do not perform all of them at once unless you have evidence of a real compromise.
First determine whether the problem is the account, the sign-in method or the destination application.
Stop unfamiliar access first, then investigate how it happened.
Administrator pages are shown only to accounts with the required permissions. The most important principle is that MemoID controls entry to an application; permissions after entry remain with that application. The cards below explain the operational effect of each menu before introducing its technical terms.
The starting point for authorized MemoID administrators to review users, registered applications, active sessions and important security signals.
Find MemoID accounts, review account availability and manage application-entry settings for individual users when your administrator role allows it.
Register applications that use MemoID for sign-in and control the approved callback addresses, access rules and application credentials.
Organize users into groups and apply the same application-entry decision to many accounts without configuring each account individually.
A chronological record of important administrative changes and security events, designed to answer who changed what and when.
This section is mainly for administrators and developers. If you are an everyday user, you can skip it safely. If you manage a production application, treat these values as controlled configuration because an incorrect change can interrupt sign-in for real users.
Application identity and client type
Registered return addresses reduce redirect abuse.
Scopes, PKCE, audience and token lifetime
Application access policy and account-specific exceptions
Applications integrating with MemoID should prefer the standard discovery information and the dedicated developer documentation rather than copying endpoint values by hand. This helps the integration remain aligned with the capabilities MemoID actually publishes.
Step-by-step integration guidance for sign-in, authorization, token handling and production deployment considerations.
Machine-readable information describing the MemoID issuer, protocol endpoints and supported capabilities.
Public verification keys used by applications to check that signed MemoID tokens were issued by the expected authority and were not modified.
Explains how an application can request MemoID sign-out and safely return users only to registered post-logout destinations.
You do not need to memorize them. Use this section as a reference when one of these terms appears on screen.
OAuth 2.0 · OpenID Connect
Different values exist for different parts of the sign-in process.
PKCE · Passkey · MFA
IP · User-Agent · AMR · ACR
Be careful with screenshots as well. Before sharing a screen for troubleshooting, cover or remove passwords, verification codes, recovery codes, tokens, client secrets and MFA setup keys. A screenshot can expose a secret just as easily as copied text.
Signing out here ends the current MemoID browser session. Signing out a device from the Devices page ends only that selected MemoID session. Signing out other devices keeps the device you are using now. Signing out everywhere is the broadest option: it ends all MemoID sessions and invalidates long-running refresh access managed by MemoID, so affected devices and applications will need to authenticate again. Remember that a destination application can also maintain its own separate session.
A few things to know before making yourself at home.
Read the full guideMemoID is the account and sign-in service for MemoLab and connected applications. It lets you manage your profile, sign-in methods, devices and application permissions in one place.
The sign-in page shows the providers currently available. If you already have a MemoID with the same email, sign in to that MemoID first, then connect the provider from Sign-in methods to keep everything in one account.
A passkey lets you sign in using your device's fingerprint, face recognition or screen lock instead of typing a password. Availability depends on your device and browser. Add one from Security in your MemoID account.
Signing in confirms your identity. Each application has its own access policy and may require an invitation or approval. Check the application's access message or ask its administrator to review your access.
From another device, open Devices and sign out the missing device. Review recent activity and your sign-in methods. If you cannot sign in, use account recovery with the email registered to your MemoID.
They do different things. Signing out ends the selected sign-in session. Disconnecting an app removes the permission you granted it through MemoID. The app may keep its own session, so use its sign-out controls too when needed.