Teams and access

Sign in to Ahamo

Sign in with email and password, with Google, Apple or GitHub, or with your company's SSO; link those accounts to yours; and set up your organisation's own sign-in apps.

On this page

You can sign in to Ahamo with your email and password, with a Google, Apple or GitHub account, or with your company's single sign-on (SSO). This page covers signing in to Ahamo itself. Sign-in for the people who use your apps is separate; see Add sign-up and sign-in.

The sign-in page

The sign-in page shows only the ways your organisation offers:

  • a row of buttons for Google, Apple and GitHub, for those your organisation has on;
  • Continue with SSO, when your organisation signs in through its company account;
  • your email and password, always.

Tick Save email and login method on this device to have Ahamo remember your email and the way you signed in on this browser. Next time the email is filled in and that button is marked Last used. Untick it at your next sign-in to forget both. Nothing is saved on a shared or private browser unless you tick it.

Sign in with email and password

Enter your email and password and choose Sign in. Use Forgot your password? if you can't remember it.

If your organisation uses company sign-in for your email address, Ahamo sends you to your company's sign-in page instead of checking a password.

Continue with SSO

Choose Continue with SSO, enter your work email and choose Continue. Ahamo sends you to the sign-in page of the company that owns your email's domain. If your organisation doesn't use company sign-in for that address, Ahamo says so and you can sign in another way.

Continue with Google, Apple or GitHub

  • New to Ahamo? Choose the provider's button on the sign-up page. Enter your workspace name first; the account is created with the provider's verified email address.
  • Already have an account? If you confirmed your email address and it's a Gmail address or your organisation's Google Workspace address, continuing with Google signs you into your account and connects it. Otherwise sign in, then open your settings and choose Sign-in › Link Google (or Apple, or GitHub). From then on you can sign in either way.

Confirm your email address

When you sign up with a password, or accept an invitation, Ahamo emails you a link to confirm your address. Your account works before you confirm it. Open the link while signed in to that account (the page asks you to sign in first if you aren't). Until you confirm, a Google account with the same address can't sign into it. To get a new link, open your settings and choose Sign-in › Send confirmation email. The link works once, for 24 hours.

Ahamo signs you in only with an email address the provider has verified. With GitHub that is your account's primary email address, even if it is private on your profile; verify it in GitHub under Settings › Emails if Ahamo says it isn't. With Apple you may choose to hide your email; Apple then gives Ahamo a private relay address that forwards to you. Apple shares your name only the first time you use it with Ahamo, so Ahamo keeps it then.

You can unlink an account in the same place, unless it is your only way to sign in.

Set up sign-in methods for your organisation

This section is for organisation admins. If your organisation is not set up on its own, Ahamo manages sign-in for you.

Open Tenant admin › Configuration › Sign-in.

  • Sign-in methods turns Google, Apple and GitHub on or off for your organisation. Off means no button, and that sign-in is refused.
  • Apps decides which app each provider names on its consent screen, one tab per provider. By default people sign in through Ahamo's app, so the provider shows Ahamo's name. Choose Use your own Google app (or Apple, or GitHub) to show your organisation's name and logo instead.

To use your own app, pick one of your organisation's domains and register the redirect address the page shows with the provider:

  • Google. In Google Cloud, create a client of type Web application under Google Auth Platform › Clients, add the address under Authorized redirect URIs, and set the Audience to In production. Paste the client ID and client secret.
  • GitHub. In your GitHub organisation's settings, register an OAuth app under Developer settings › OAuth Apps with the address as its Authorization callback URL, and generate a client secret. Paste the client ID and client secret.
  • Apple. In Apple Developer, create a Services ID with Sign in with Apple, add your domain and the address as its Return URL, and create a key with Sign in with Apple. Paste the Services ID, Team ID, Key ID and the key's .p8 file. A new Apple app starts off, so test it, then turn it on.

Save, then choose Test with the provider. Secrets and keys are stored encrypted and never shown again. If the provider shows an error at the first real sign-in, the page lists the usual causes and their fixes. Turning your own app off or removing it sends people back to Ahamo's app. Each change is recorded in your organisation's audit log.

If people may hide their email with Apple, register the domains Ahamo sends your email from with Apple (Sign in with Apple for Email Communication), or invitations and password emails to their relay addresses are dropped. The Apple tab explains how.

Your organisation's own Google app for Ahamo sign-in is separate from the Google sign-in app used by Google connectors, which is set up under Configuration › Connectors. See Connect the tools you already use.

If you can't sign in

  • "Invalid email or password." Check both, or use Forgot your password?.
  • "Google sign-in is turned off for this organisation." (or Apple, or GitHub) Use your email and password, or another way your organisation offers.
  • "No Ahamo account uses this GitHub account yet." Sign up with it, or sign in another way and link it in your settings.
  • "There's already an account for this email." Sign in with your password, then connect the account in your settings under Sign-in, or confirm your email there first.
  • "Your GitHub account has no verified primary email address." Verify one in GitHub, then try again.

Next, see Create and switch Workspaces or Workspace members.

On this page