Where you sign in
Your workspace has its own address (for exampleacme.app.us.dippr.ai). Sign in there, not on the shared
login page: that page belongs to whichever workspace’s subdomain you’re on. If you don’t know your
workspace’s address, ask an administrator. Platform operators who run their own Dippr deployment sign in
on the separate admin console address instead.
If your account belongs to more than one workspace and you aren’t following a link to a specific
page, sign-in takes you to a picker titled Choose where to sign in (“You belong to more than
one. Pick one to continue.”), listing your workspaces by name. Picking one takes
you to that workspace’s address. If you followed a link to a page, sign-in continues to that page.
If the workspace list cannot load, you can still sign in at a workspace address where your access
is confirmed, continuing to the page you requested. The shared sign-in page offers Retry until
it can load the list for you to choose from.
A brand-new account that still has to create its first workspace goes straight to the creation form
even when the list cannot load, because there is nothing to choose from.
Likewise, if you reach the shared sign-in page asking for the creation form (for example, after
choosing Create workspace when your session had expired), you go to the form even when the
list cannot load; the form offers its own Retry.
Switching workspaces
The workspace switcher at the bottom of the console sidebar shows your current workspace’s name. Open it to see the other workspaces you belong to, each with its name and address. Choose one to open that workspace at its own address. Your permissions follow your roles in the workspace you open. The switcher also works when the sidebar is collapsed. Use Tab to reach it and Enter or Space to open it. Press Escape while focus is in the switcher, or click outside, to close it. In the collapsed sidebar the switcher shows the first letter of your current workspace’s name. While the list loads, wait for your workspaces to appear. If loading fails, choose Retry to load the list again. On the shared console address (the one without a workspace name in it) there is no current workspace, so the switcher is labelled Workspaces and its menu lists your workspaces and Create workspace without a “Current workspace” heading. If you belong to only one workspace, the switcher shows that workspace and Create workspace. Choose Create workspace to create another workspace, even if you joined your current workspace by invitation. The form explains the creation limit when you reach it. If you open the shared console address (the one without a workspace name in it) while signed in, there is no workspace to show, so you are taken to the same place sign-in would take you: straight to your workspace if you belong to only one, or to the Choose where to sign in picker if you belong to several. If you opened a specific page (for example the Queries page), that page opens in the workspace you land in or pick. A platform administrator is treated the same way for workspace pages. If an administrator opens an operator page such as Tenants on the shared address, that page opens on the operator-only platform admin console, even when they belong to tenants. An administrator with no workspace, or whose only workspace has no address available, goes to the operator-only platform admin console instead. An account that still has to create its first workspace goes to the creation form. Signing in with an identity provider after choosing Create workspace also ends on the creation form, the same as signing in with a password. You can still open a workspace directly by its address or a bookmark. The sign-in picker remains available when you sign in to an account with several workspaces.Password sign-in
1
Enter your email and password
Type the email and password your administrator gave you, or the ones you set when you accepted an
invitation. See Accepting an invitation if you haven’t set a password yet.
2
Sign in
You land on the page you were trying to reach, or on the workspace’s home page if you came
straight to the login page.
Sign in with a provider
Below the password form, Dippr shows one button per identity provider your workspace has configured — for example Sign in with Google, Sign in with GitHub, or Sign in with Email. Click one to authenticate with that provider instead of typing a password; you’re returned to Dippr already signed in. The button list reflects what your deployment actually offers:- One button per named provider (Google, GitHub, Email) it has configured.
- A single generic Sign in with SSO button when your workspace connects an outside identity provider (Okta, Azure AD, or another OpenID Connect provider) that isn’t one of the named ones above.
No social sign-in providers are available.when none are configured — use the password form.
Signing in with a provider does not connect that provider to an existing account just because the
provider reports the same email. Use the account’s existing sign-in method. Connecting another
provider requires an authenticated linking flow when your deployment offers one.
Sign in with Email
If your workspace offers Sign in with Email, you don’t need a password or a company identity provider. Click the button, type your email, and you get a one-time code to confirm it. Enter the code and you land in the console.Password recovery and Email sign-in
Sign in with Email appears with the other provider buttons when your deployment offers it. It is not a password-reset link for an unlinked password account.- If you set a password and have not connected Email from an authenticated account-linking flow, Sign in with Email is refused for that address. Your password and existing sessions keep working.
- If you already sign in with another provider, such as Google, Dippr tells you which one to use instead.
- If the page has no Sign in with Email button, your deployment has no Email sign-in. Ask an administrator for help.
One session, several workspaces
Signing in once covers the whole session. You don’t need to sign in again to move between workspaces you belong to, or between the console and its settings pages.Signing out
Sign out is at the bottom of the sidebar, under your account. It ends your Dippr session everywhere: every workspace you belong to, the console and its settings pages. The next Sign in with Email always asks for your email and a fresh code, even if you signed in a moment ago. That is deliberate. On a shared or borrowed computer it is what stops the next person being signed straight back in as you.Signing out of Dippr does not sign you out of an identity provider you reached Dippr through. If you
signed in with SSO, your provider may still have you signed in on that computer, and Sign in with
SSO can return you to Dippr without asking again. The same holds for Sign in with Email: the
email provider may still have its own session on this device — the next Email sign-in always asks for
a fresh code, so no one is handed your account silently, but on a shared or borrowed computer sign out
of the browser or close the session as well. Sign out of the provider too when you’re finished on a
computer that isn’t yours.
Errors you might see
The first administrator
A freshly deployed Dippr has no members yet. Whoever deploys it configures a first administrator account as part of setup; that person signs in, creates the workspace, and invites everyone else (see Inviting a user). If you’re setting up a new deployment, your deployment documentation covers how that account is configured. Every later workspace usually doesn’t need this step: anyone can create their own workspace by signing up, where a deployment allows it — see Create a workspace.Related
Create a workspace
Sign up and get your own workspace with no invitation needed.
Inviting a user
Add someone to an existing workspace instead.