Identity and people

Invite your team and set roles

Create or join your organization and give people the access they need.

Deployment
BYOC and self-hosted

An organization is a separate tenant. Your account needs tenant membership before you can enter the console. An administrator can invite your email before you create a Diakrin account.

Create or join a tenant BYOC only

Diakrin onboarding can create your first tenant and assign its first owner's email before signup. Sign in or create an account using that exact email and complete email verification. An active email assignment or authorized invitation attaches the verified account automatically.

If you see Tenant access required, ask your administrator to check the recipient email and invitation validity, then select Retry tenant access. Use an invitation accepts a supplied code as a fallback.

Once you belong to a tenant, open your avatar menu to switch between your authorized tenants, Join tenant, or Create tenant. The tenant name in the header is a breadcrumb; it does not grant access. Joining another company's tenant requires their authorization.

Choose the right role

RoleOrganization access
OwnerManages organization ownership, members and settings
IT administrator (Admin)Manages members, policies, budgets, SSO and SCIM, and approves requests; cannot change owners or other admins or delete the organization
MemberSees the projects they are assigned to and uses apps they are given access to; needs an explicit project or app assignment
BuilderBuilds within assigned apps; new app creation follows the company’s policy
Technical administratorCreates, approves and runs infrastructure setups, manages their secrets (never reads the values), operates deployments and sees every project; cannot manage people, policies or budgets, and cannot approve plans or read audit logs

Use Member or Builder for people who should work only within assigned apps. IT controls who can create new apps and whether approval is required. Use Technical administrator for infrastructure operators. People who only need to look at a project or use an app are Members with that project or app assigned.

Project permissions are a separate layer. Being a member does not automatically authorize deployments, company data or administration. Identity-provider group names do not assign these roles.

Invite a colleague BYOC only

  1. Select the correct organization in the header or avatar menu and open Get started → Set up the company → Invite your team, or Settings → Members.
  2. In Organization people, enter Invited email and choose Invitation role. Member is the default.
  3. Select Send invitation. Diakrin emails the person a link to join, and Pending invitations shows the email status (Sending, Email sent, or Email could not be sent).
  4. If the email could not be sent, or your installation has no email provider set up, select Copy invitation link and share the link through your approved company channel. The link and its code are shown only once, right after you create the invitation.
  5. Ask them to open the link and sign in using the exact invited email, verifying it if asked. They attach automatically while the invitation is active. If the link does not open, they can choose Use an invitation or Join tenant and paste the code.
  6. Assign the apps or shared projects they need. Admin invitations require an Owner; ownership is changed explicitly after joining.

Invitations are single-use and expire after seven days. Select Resend invitation to send a fresh link and email; the earlier link stops working. Revoke an unused invitation if it was misdirected. Create a fresh authorized invitation for expired ones or for a removed member who needs to rejoin.

Each person in Organization people carries a small Local or SSO label that shows where they sign in. An organization can have several owners. The only owner cannot leave or change their own role: make someone else an owner first.

Add a person on a self-hosted installation Self-hosted only

  1. Open Settings → Members. The Add a person card replaces invitations.
  2. Enter the person's Email and choose a Role: Member (the default) or Builder. The IT administrator option appears only for the workspace owner.
  3. Enter a Temporary password of at least 15 characters, or select Generate for a random 24-character one. Use Show password or Copy password to pass it on.
  4. Select Add person. The confirmation names the person and role, and the member list refreshes.
  5. Share the email and temporary password through your company's approved channel. Diakrin does not send it, and it is not shown again.

At first sign-in they must replace the temporary password before anything else works. Owners and admins then also set up an authenticator app (see Administrator second factor). Only the owner can create an admin; admins can add members and builders. People who sign in through company single sign-on do not need a local account.

Reset a local password Self-hosted only

The console offers Reset password to the workspace owner, on other members' rows.

  1. Open Settings → Members and select Reset password on the person's row.
  2. Select Create reset token. Any earlier token for that person stops working.
  3. Copy the one-time token and share it through your company's approved channel. It expires in 30 minutes and is not shown again; select Done to close it.
  4. The person opens the console address, chooses Recover account, and enters their email, the token and a new password.

A reset needs a sign-in from the last 15 minutes. If the console asks you to sign in again, do so and retry. People who sign in with company single sign-on reset their password there.

Administrator second factor Self-hosted only

Owners and admins who sign in with a password must also use an authenticator app (TOTP). Your first sign-in asks you to add Diakrin to your authenticator and confirm one code. You then get eight recovery codes, shown once. Keep them somewhere safe: each works once.

  • New session: enter the current 6-digit code. Nothing else loads until you do.
  • Lost phone: sign in with your password and choose Use a recovery code.
  • Lost phone and codes: another administrator resets your factor, or your installation operator runs the owner recovery with the reset option.
  • After a reset: sign in straight away to add your new authenticator. Until you do, anyone with your password could add theirs, so change the password if others may know it.
  • Builders and members are not asked for a second factor.
  • New administrators first replace the temporary password the owner gave them, then add their authenticator.

Change or remove access

Review role changes carefully: they revoke existing project grants and coding-tool tokens in that organization. Reassign the access the person should retain after the change.

Remove a person through Organization people when they leave. Owners can manage every role; admins can manage Member, Builder and Technical administrator. The final Owner cannot leave or demote themselves until another Owner is in place.

See Troubleshooting and help for invitation failures or a missing organization.

Next stepProvision people from your identity provider →