Account settings is your personal page in the Stacktape Console. Open it with Account in the profile menu at the top right. It holds your name and the ways you sign in, and it shows where you are signed in. These settings belong to you, not to an organization, so they apply in every organization you are a member of.
Rules that an organization sets for all its members, such as requiring two-factor sign-in or single sign-on, are on Members and Single sign-on.
If you used the Console before v4
Stacktape v4 moved Console sign-in to a new system. Your account, organizations, roles and API keys did not change. A few things work differently:
- Password. The first time you sign in with your email and password, Stacktape checks the password against the old system and keeps it. If your password is not accepted, use Forgot password? on the sign-in page to set a new one.
- Authenticator app. If you used one before, the sign-in page asks for its code once more. The old authenticator does not carry over: after that sign-in, Account settings asks you to set up an authenticator app or a passkey again. Until you do, a password sign-in does not count as two-factor, and an organization that requires two-factor sign-in stays closed to you. SMS codes are no longer offered.
- Google. Sign in with Google as before. Your account is matched by its verified email address.
- CLI.
stacktape loginnow asks you to approve the sign-in in the browser. See login.
Profile
- Name is shown to your teammates. Edit it and click Save.
- Email is the address you sign in with. It cannot be changed on this page.
Ways to sign in
You can have several ways to sign in at once. All of them except a password alone count as two-factor sign-in, which matters when an organization requires it.
| Way to sign in | Where you set it up | Counts as two-factor |
|---|---|---|
| Password | When you sign up, or with Forgot password? | No |
| Password and authenticator app | Authenticator app on this page | Yes |
| Passkey | Passkeys on this page | Yes |
| Google or GitHub | Google and GitHub on this page | Yes |
| Single sign-on | Your organization's identity provider | Yes |
Password
Change your password
- In the Password row, click Change password.
- Enter your Current password, then the New password twice.
- Click Change password.
A password must have at least 8 characters (at most 128) and must not appear in a known data breach. Stacktape checks this with Have I Been Pwned, which receives only the beginning of the password's hash, never the password.
After the change, this browser stays signed in and every other browser and device is signed out. CLI logins
(stacktape login) and API keys keep working; see Sessions for how to end them.
Add a password or reset a forgotten one
If you signed up with Google or GitHub, the Password row shows None. To add a password, or to replace one you forgot:
- Sign out, and on the sign-in page click Forgot password?.
- Enter your email and click Send reset code.
- Enter the Reset code from the email and your New password, then click Change password.
A reset signs you out of every browser and device. Sign in again with the new password.
Authenticator app and backup codes
The Authenticator app row appears when your account has a password. With it on, a password sign-in also asks for a 6-digit code from an app such as 1Password, Google Authenticator or Microsoft Authenticator.
Turn it on
- In the Authenticator app row, click Turn on.
- Enter your password and click Continue.
- Scan the QR code with your authenticator app. If you cannot scan it, copy the secret shown under the code into the app instead.
- Enter the 6-digit code from the app and click Turn on.
- The Save your backup codes dialog shows 10 backup codes. Copy them to a safe place, such as your password manager, and click I saved them.
The backup codes are shown only once. Each code signs you in once instead of an authenticator code. Without the codes, a lost phone can lock you out unless you have another way to sign in, such as a passkey or Google.
The change counts from your next sign-in. If an organization requires two-factor sign-in, sign out and sign in again with your password and a code to open it.
When you sign in, the Two-step verification screen asks for the code. If you do not have your phone, choose Use a backup code.
Turn it off
Click Turn off and confirm with your password. Your password sign-ins stop asking for a code, so organizations that require two-factor sign-in then need you to sign in with a passkey, Google or GitHub.
To move the authenticator to a new phone, turn it off and on again. The old entry in your authenticator app stops working.
Passkeys
A passkey signs you in with your device's fingerprint, face recognition or PIN instead of a password. It counts as two-factor sign-in on its own.
- In the Passkeys row, click Add passkey.
- Follow your browser's or password manager's prompt.
Passkeys are named Passkey 1, Passkey 2 and so on, with the date each was added. To use one, click
Sign in with a passkey on the sign-in page.
To remove a passkey, click Remove next to it. Also remove it from your device's password manager, which keeps offering it otherwise.
Google and GitHub
The Google and GitHub rows let you sign in with those accounts. Click Connect and approve the request at the provider.
The provider account must have verified the same email address as your Stacktape account. Otherwise it is not connected, and the page says which address it needs.
Disconnect removes the connection. You cannot disconnect your only way to sign in; add another one first.
Sessions
The Sessions row lists the browsers signed in to your account, with the browser and system, IP address and when each was last active. This browser marks the one you are using.
- Sign out next to a session signs that browser out at its next request.
- Sign out everywhere else ends every session except this one.
A browser that is not used for 30 days is signed out. Changing your password also signs out every other session.
CLI logins are not browser sessions and do not appear here. Run stacktape logout on a machine to end
its CLI login. Owners, Admins and Developers also see their CLI logins as CLI session on the
API keys page and can revoke them there.
Delete your account
Account deletion is not self-service. Email support@stacktape.com from the address you sign in with.
What organizations see
Changes on this page are recorded in the audit log of every organization you belong to: password changes, the authenticator app turned on or off, passkeys added or removed, Google or GitHub connected or disconnected, and sessions ended. Sign-ins themselves are not recorded. Owners and Admins can also see on the Members page whether you have two-factor sign-in.
Troubleshooting
The authenticator code is rejected
Codes change every 30 seconds. Enter the current one, and check that your phone's clock is set automatically. If codes are still rejected, sign in with a backup code or another way, then turn the authenticator app off and on again.
I lost the phone with my authenticator app
On the Two-step verification screen, choose Use a backup code. You can also sign in with a passkey, Google or GitHub if you added one. Then turn the authenticator app off and on again with your new phone. If you have none of these, contact support@stacktape.com.
"Google was not connected" or "GitHub was not connected"
The provider has not verified the email address of your Stacktape account. Verify that address at the provider, or connect a provider account that uses the same address.
"This organization requires two-factor sign-in"
Set up an authenticator app or a passkey on this page, then sign out and sign in again with it.
"This organization requires single sign-on"
Sign out, then on the sign-in page click Sign in with SSO and enter your work email. See Single sign-on.
Related features
- Team and access control: members, roles and the two-factor requirement
- Single sign-on: sign in through your organization's identity provider
- API keys: keys and CLI sessions for the CLI and CI
stacktape login: sign in to the CLI