Protect your GraphOps account and keep a working way to sign in when you replace a device or disconnect a provider. Your account holds your personal sign-in methods and sessions; organization roles control what you can do in each team.
Create an account or sign in
Create account Sign inChoose email or an available Google or GitHub sign-in option. Provider options depend on which methods are enabled. Complete any requested profile details and email verification before continuing to your organization.
If GraphOps finds an existing account for your email, follow the sign-in and connection prompts to prove that account belongs to you. Review the account shown before confirming a connection. If you are accepting a team invitation, use the account with the invited email address.
Find your verification email
The GraphOps verification email contains a verification code and a link. Enter the code on the page where you started, or open the link. Both expire at the time shown in the email.
Check your inbox and spam or junk folder for the GraphOps verification email. If it was marked as spam, mark it as Not spam. Choose Haven’t received it? on the verification page to resend, then use the code or link from the latest email.
When you start with Google or GitHub, finish sign-in in the browser where you began. A verification link opened elsewhere can verify the email, but you still need the original browser to continue that sign-in attempt. If the attempt has expired, start sign-in again.
Open your account settings
In the platform, choose Account from the sidebar or your account menu. You can manage your personal sign-in methods even before joining an organization.
Available methods show whether they are configured or disabled by policy. Complete the sign-in check when prompted before changing credentials, connecting a provider, or removing a method. After returning to Account, check that the method's status or entry reflects your change.
Set a password or add a passkey
Under Sign-in methods:
- Choose Set up password or Change password below Password, then follow the sign-in and password prompts.
- Choose Add passkey and follow your browser or device's enrollment prompts. After returning, check that the named passkey is ready before relying on it.
You can sign in with a passkey instead of your password. A passkey verifies you on your device, so it also counts as two-factor authentication. To require a second factor when you sign in with your password, set up two-factor authentication.
If setup was interrupted and Check setup appears, use it to confirm the previous result before starting another setup. If you cannot sign in with your password, use password recovery from the sign-in page.
Connect Google or GitHub
Connecting a provider lets you use it to sign in to the same GraphOps account.
- In Account, find Connected accounts.
- Choose the available Connect Google or Connect GitHub action.
- Sign in to the intended provider account, complete the requested GraphOps account verification, and confirm the connection.
- Check that the provider and account appear in Connected accounts.
A provider with a different email can be connected to your existing account. Connecting it does not change your GraphOps account email or move your organization memberships.
Disconnect a provider
Keep another working sign-in method before disconnecting a provider. GraphOps requires proof using another permitted method and prevents removal of your last usable sign-in method. An authenticator app or a security key used only as a second factor does not replace a primary sign-in method.
Open the connected account's action menu, choose Disconnect, and complete the verification and confirmation. Check that the connection disappears when you return. Disconnecting a provider does not end existing GraphOps sessions; use the session controls below when you also want to end access from a device.
Add two-factor authentication
Use Two-factor authentication to add another check to your sign-in:
- Choose Set up authenticator to enroll an authenticator app and confirm its code. Once enrolled, use Manage authenticator to manage it.
- Choose Add security key to enroll a security key, or Manage security keys to manage existing keys.
Follow the hosted sign-in prompts and check the configured status when you return. Adding or removing an authenticator app shows on Account as soon as you return. If GraphOps says the change was saved but is not ready, or could not be confirmed, open Account again to check its status before changing it again.
Two-factor authentication requires a second factor in addition to your password. Signing in with a passkey already satisfies both. Your sign-in policy determines which methods are available and whether a second factor is required; it can prevent removal of a required factor.
Remove a passkey
Before removing a passkey, make sure you can sign in with a password or a connected provider. Passkey removal requires fresh proof with one of those methods; another passkey alone is not sufficient.
In Passkeys, open the named key's action menu, choose Remove passkey, and complete the verification and confirmation. Check that the key disappears from the list. Enroll a replacement before removing a key you still depend on.
End a device session
Review Sessions for devices you no longer use or do not recognize. Compare the device, IP address, and update time before selecting a session. The IP address is recorded when that session starts. It can be shared by people using the same network or VPN, and it does not change when you view the list from another connection. Older sessions can retain an address recorded before an IP collection correction.
Completing a sign-in check from Account signs you in with a new session on that browser and ends the session it replaced, so repeated checks do not add sessions.
To end a session, open its action menu, choose End session, and confirm. Check that the session is removed. Ending your current session signs you out, so sign in again to continue.
Ending a device session also ends existing support account access across your signed-in tabs. Reload the platform from a session you kept to reconnect support.
If a removal was interrupted and Check removal appears, use it to confirm the outcome before attempting another removal. If the result remains unresolved, contact support with the action, approximate time, and displayed error. Never send passwords, verification codes, or session credentials.