Inviting someone
Go to Settings → Users and click Invite user. You need the Members · create privilege (see Roles and permissions matrix for which built-in role holds it).1
Enter the email
Type the email address of the person you’re inviting.
2
Pick one or more roles
Choose every role the invitee should join with. Nothing is pre-selected, and an invite never adds a
role you didn’t pick. Someone who is already a member keeps the roles they have: the link changes
nothing for them, so change their roles from the members list instead. Everyone (
public) isn’t offered because every other built-in role already includes
it; grant it from the members list if someone holds only a custom role that doesn’t. You can change
their roles later from the members list, so this doesn’t have to be final.3
Create the invite link
Dippr generates a one-time link. Copy it now: it’s shown only once and isn’t stored anywhere you
can come back to. Send it to the person however you normally would (chat, email, whatever you use).
An invite adds the invitee to your tenant with the roles you picked. It never changes how they
sign in: if the invited email already has an account (through a password, Google, GitHub or Email),
that account’s sign-in method stays exactly as it was, and the person joins only after they accept the
invitation while signed in. See
If the invitee already has an account below.
You can only invite someone into a role that’s within your own permissions. You can’t hand out a role
you don’t hold yourself; if you try, the invite is refused rather than created. The same check runs
again when they accept: any role you can no longer grant by then is dropped (all of them, if the role
service can’t be reached), and they still join. Check the members list afterwards and grant anything
missing.
From the command line
dip member invite <email> --role <name> mints the same one-time link and prints it, so an admin or
their agent can invite without opening the console. Repeat --role for more than one role; with none,
the invitee joins as viewer. It needs the same Members · create privilege and a credential
holding members:invite. A current dip login already holds that scope. An older or narrowed login
asks for members:invite only. For an API key, mint members:invite for a service user whose roles
allow inviting; governance:manage alone cannot invite.
unchanged with the role they hold. A login checks only when it already holds
governance:manage. An API key attempts the check and skips it if access is refused. Neither asks
for extra permission. With --json, member_checked says whether the check ran. When it did not,
dip says so; an existing member who accepts gains no membership or role.
An invitation that has not been accepted yet is not visible to dip, so inviting the same person again makes a new link; the earlier link keeps working until it is used or expires. With
--json, the link is in invite_url. It carries a one-time secret, so hand it only to the person
you invited. When it invites someone, the command also prints a line for them to paste into their AI after they join; with
--json it is agent_prompt. It names your tenant’s address only, so it is safe to share. See the command reference for the credential it needs.
Accepting an invitation
Opening the link takes the invitee to the Accept your invitation page. Before you submit, the page shows the invited email, tenant name and offered roles. Offered roles are the roles on the invitation; they are assigned when you join, subject to the inviter’s permission to grant them. Reading this context does not accept the invitation and does not reveal whether the email has an account or which sign-in methods it uses. When the password form creates a new account, you are signed in automatically and taken to the tenant home, or the safe destination you were opening. You do not need to verify your mailbox first. If automatic sign-in fails, use Go to sign in. Existing accounts still sign in the way they already do and accept the waiting invitation. The steps below describe the screens that remain available when you need to sign in manually.1
Choose a password, or sign in
New to Dippr? Choose a password of at least 12 characters; the confirmation field must match.
Already have a Dippr account? Choose Sign in to accept under the form instead. You don’t type a
password, and the next screen says how to continue (see
If the invitee already has an account). The page does not
say whether the email has an account.
2
Continue
This sets the password and joins the invitee to your tenant with the roles you picked — unless
that email already has a way to sign in, see below.
3
Sign in
After you submit, the screen tells you how to continue, with a link to
sign in. It names the invited email address, and the tenant when its name
can be looked up. Both are also shown before you submit. Below that it shows a line to paste into
your AI, with a Copy prompt button, so your AI can read your tenant’s
/agents.md and connect
once you are signed in. The line never contains the invitation link.- “this invitation has expired — ask the person who invited you to send a new one” — the link aged out (invites expire 3 days after creation). Create a fresh invite; the old one can’t be revived.
- “this invitation has already been used — try signing in instead” — someone already accepted it and set a password, so the account exists. The invitee should sign in rather than accept again.
- “invite is invalid, expired, or already used” — the generic answer for a link Dippr doesn’t recognize at all. It’s kept deliberately vague so a random or mistyped token can’t be told apart from a real one; a genuine invite gets one of the specific messages on this page.
- “this email address already belongs to a different organization, so it can’t join this workspace. Ask whoever invited you to send the invite to a different email address”: the invited address already has a Dippr account tied to a different organization, and Dippr does not yet support one account belonging to tenants in two organizations. Signing in with the existing account does not add this tenant to it, and there is currently no self-serve fix. Send a new invite to a different email address.
If the invitee already has an account
An invite link proves who created the invitation, not who owns the mailbox. So when the invited email already has a Dippr account (a password, or a Google, GitHub or Email sign-in), opening the link does not add that person to your tenant. The invitee chooses Sign in to accept on the Accept your invitation page, without typing a password, and the invitation waits for the account holder to accept it. If they fill in the password form instead, that password is discarded rather than replacing what the account already uses. The link opens even when the browser is already signed in to another tenant. The invitee sees:One more step This invitation is for alex@example.com to join Acme Analytics. This email address already has a Dippr account, so you have not joined yet. Sign in to that account and accept the invitation.When they filled in the password form instead, the screen adds “The password you entered was not changed.” The Sign in to accept button on this screen opens the console of the tenant the browser is already signed in to. If the browser isn’t signed in, it opens the invited tenant’s sign-in page instead, and after signing in the invitee lands in their own tenant’s console, or on the invitation itself when they belong to no tenant yet. The invitation appears at the top of the page with who invited them, the tenant and the roles. They choose Accept to join, or Decline to turn it down. If the browser is signed in to a different account, the invitation isn’t shown there. In that case they choose Signed in as someone else? Use a different account, which signs that account out and opens the invited tenant’s sign-in page for the invited account. A person whose invitation is waiting is not a member. They don’t appear in the members list, can’t open your tenant, and hold no roles until they accept.
- Expiry: a waiting invitation expires after 30 days.
- Cancelling: an admin of your tenant can cancel it under Settings → Users in Waiting for acceptance. See Manage members.
- Already a member: if the account is already a member of your tenant, opening the link changes nothing. The invitee sees You already have an account: “You are already a member of this workspace. Sign in the way you normally do to open it.” After the password form, it adds that the password they entered was not changed.
- No account after all: if someone chooses Sign in to accept but the email has no Dippr account yet, opening the link creates the account as usual, with a generated password. The page shows that password once on Save your password, with a copy button. Go to sign in stays disabled until they tick I have saved this password; then they sign in with it.
Can an invited account add a provider by email?
No. A provider sign-in cannot connect itself to an existing account only because it reports the same email. This rule applies to Google, GitHub, Email and SSO. The provider sign-in is refused before it changes the account. The invitation password, browser sessions, command-line sessions and MCP connections keep working. Roles, memberships and API keys are also unchanged. What this means for you:- Keep using the password you set when you accepted the invitation.
- If a provider sign-in says an account already exists, use the existing sign-in method or ask an administrator for help.
- Connecting another provider requires an authenticated linking flow when your deployment offers one.
- A provider that was already linked to the account keeps working with its stored identity.
If they try SSO first
Related
Manage members
Change a member’s roles, or remove them from your tenant.
Sign in to your tenant
Password sign-in, identity providers, and what to do when sign-in fails.