A workspace is your team’s space in Dippr, with its own address, members, roles, integrations and data. Create one when you first sign up, or create another with the account you already use; you become its first administrator.
Self-serve sign-up is available only on deployments where it’s turned on. If the sign-in page has no Create an account link, ask whoever administers your deployment for an invitation instead. See Inviting a user.

Signing up

1

Start from the sign-in page

Click Create an account below the sign-in form.
2

Choose how you sign up

Pick Google, GitHub, or Email (Email appears only when your deployment has it configured) and authenticate with that provider.
3

Name your workspace

On Name your workspace, type a name. The address is derived from it and shown underneath as you type (accented letters are written plain, so “Café Analytics” becomes cafe-analytics); neither can be changed later. If the name has no Latin letters or numbers to build an address from, an Address field appears so you can choose one — up to 63 characters, lowercase letters, numbers and hyphens only. Product-like addresses such as www, app, api, admin, login, support and dippr are reserved and cannot be claimed by a new workspace.
4

Create your workspace

Click Let’s go. You land on your workspace’s own address, <slug>.app.<domain>, on its Overview, whose Get started card hands your coding agent one prompt (see Your first run). If setting it up takes longer than a few seconds, the form shows Setting up <slug>.app.<domain>… and opens the workspace on its own when it is ready.

Creating another workspace

Any signed-in person can create a workspace when self-serve creation is enabled. You do not need an administrator role in a workspace you already belong to. If someone invited you as a viewer, you can create your own workspace and become its administrator while staying a viewer in theirs. When creation is disabled, both your first workspace and any additional workspace are refused. You can still sign in to workspaces you already belong to. Open the workspace switcher at the bottom of the console sidebar and choose Create workspace. This opens the creation form at the shared console address. You can also open that address directly, for example https://app.us.dippr.ai/onboarding. Name the new workspace and click Let’s go. You can have up to 3 workspaces that you created and that still exist. Workspaces you joined by invitation do not count toward this limit. A creation that is still in progress or has an uncertain result also counts until it is resolved. An address collision that did not create a workspace does not count; correcting it checks the limit again. A workspace being deleted counts until deletion finishes. Create workspace remains available when you reach the limit; the form explains why you cannot create another. The new workspace joins the organization your account already belongs to, so the cross-organization invitation restriction is unchanged. The form keeps your draft in this browser for your signed-in account. If you reload or retry, continue that draft; a retry resumes the same creation instead of creating another workspace. While the workspace is being set up, the form shows Setting up <host>… and keeps checking on its own, then opens the workspace when it is ready. You can close the page: setup continues, and reopening the form picks the wait back up. A workspace being set up is not listed as a Back to link, because its address does not open until setup finishes. While creation is in progress, or its result is uncertain, the name and address stay locked so a retry uses the same details. If you are told you made too many attempts, nothing was created, so the name stays editable unless an earlier attempt’s result was uncertain. If the address is taken, you can edit it before retrying. Choose a name that changes the previewed address. Changing only capitalization or punctuation may leave the address unchanged; the form keeps it editable and reports that the address is still taken. The saved draft is cleared after successful creation. If a request cannot be completed or conflicts with an earlier attempt, the name becomes editable again: editing it, or clicking Start over, begins a fresh request. Starting over does not remove an existing workspace or increase your limit. It is unavailable while creation is in progress or its result is uncertain. The form shows a Back to link for each workspace you belong to. These links remain available when you reach the creation limit. Choose one to return to that workspace. Your role in each workspace stays separate. If your workspace list could not be loaded in full, the form says the Back to links may be incomplete and offers Retry. Retry loads the list again; until it succeeds, treat the links as only the workspaces known so far.

What you get

You land on the new workspace holding the account_admin role, with full control of its member roster and roles, so you can invite the rest of your team immediately. See Inviting a user and Roles and permissions matrix for what that role can do.

Where the workspace runs

A workspace you create this way runs on a data plane Dippr operates for you. Settings → Data planes shows:
“This workspace runs on <slug>. It’s managed automatically by us — registering a data plane of your own is optional.”
with a vendor chip on that row. You can still register your own plane later if your data needs to stay inside your own cloud account. See Data planes overview.

Why can’t I create a workspace?

Sign in to your workspace

Password sign-in, identity providers, and what to do when sign-in fails.

Inviting a user

Add someone else to your workspace instead of them signing up on their own.

Data planes overview

Where your connectors, engines and apps actually run.

Set up a workspace

The ordered checklist for everything else a new workspace needs.

Deployment address

Your deployment’s app.<domain> address is separate from an existing tenant’s <slug>.app.<domain> address. If the tenant opens but the deployment address has a certificate or connection error, ask your deployment operator to check that address’s DNS and certificate. When tenant creation is closed, sign in to your existing tenant or ask its administrator for an invitation.