Give your team dashboard access
The people who run your identity tenant sign in to the dashboard at www.udibo.com with their own Udibo accounts. What each of them can do comes from a seat on the tenant's Team page, or from an organization that holds access to the tenant. This guide covers inviting people, choosing their access level, removing them, and handing the tenant to an organization.
The people who sign in to your application are a separate population. Roles and permissions you give them never open the dashboard, whatever they are called; see what we promise.
Who owns a tenant
When you create a tenant with Personal active, your account gets its Owner seat. With an organization active, the organization becomes the owner instead, which takes an owner membership in it, and its owner and admin members then administer the tenant. A tenant has exactly one owner: a person, or an organization. Ownership moves only by transfer, so Owner is never offered when you invite or add access, and the Owner seat cannot be revoked. A revoke that would remove your own last way into the tenant is refused too.
Choose an access level
| Access level | What it can do |
|---|---|
| Admin | Every dashboard section and management API operation except the Owner-only ones below, including application and webhook secrets. Can grant and revoke Admin and Support seats |
| Owner | Everything Admin can do, plus credential export and managing billing. Held by one person or organization, and moved only by transfer |
| Support | Reads that are not marked sensitive, plus impersonating a user. Nothing that writes, and no secrets or exports. Support can see who has access but cannot change it |
A person's access is everything their seats carry together, and the levels stack. Support is narrower than Admin rather than an addition to it, so give one or the other, not both.
Secrets are separate permissions. Creating or rotating an application's client secrets needs Reveal application secrets, and revealing or rotating a webhook signing secret needs Reveal webhook signing secrets. Admin and Owner carry both; Support carries neither. Without the permission, the application or endpoint page hides those controls and says which permission is missing.
When an organization owns the tenant, the access list can also offer roles that organization defines. You can give someone such a role only when it carries nothing you lack yourself.
Invite a team member
The person needs a Udibo account first. Invite the email address they signed up with.
In the dashboard, open your tenant and choose Team in the Tenant group.
Under Invite a teammate, enter their Email address.
Pick an Access level. The list shows only the levels you may grant, and never Owner.
Choose Send invitation.
They appear under Direct seats with Invitation pending. The emailed link expires in 7 days and works once. They open it while signed in to that same Udibo account, choose Accept invitation, and land on the tenant's dashboard. If no Udibo account uses the address, the page says so and sends nothing.
Inviting and removing people needs the Manage who has access permission. Without it, the page shows who has access and nothing more.
If a link expires or becomes invalid while the row still says Invitation pending, open Edit access, choose Revoke beside that pending seat and confirm, then send a new invitation to the same address. There is no resend control; another invitation for the same access is refused while that pending seat exists. If the link belongs to another signed-in account, sign out of www.udibo.com and reopen it while signed in to the invited account.
Change or remove someone's access
Each person has one row, whatever they hold. Choose Edit access on the row.
Add access offers only levels that would add something. Someone who has already accepted a seat gets the new one at once, with no second invitation.
Revoke beside a seat opens a confirmation. Their access ends on their next request; the dialog says what they keep.
Access through an organization
An organization on Udibo can hold access to a tenant instead of a person. Its owner and admin members then administer the tenant through it, and they are listed under Access through organizations. Who is in the organization is managed from the organization. Revoke there ends that organization's access for every member it admitted. An organization's Owner access cannot be revoked; it moves only by transfer, which only the organization's owners can start.
Your active organization
The dashboard works in your active organization, which you pick from the organization menu in the top bar, or in Personal when none is active. Your access to a tenant never depends on it: you can open every tenant you hold a seat on, through any organization.
The tenant switcher lists the active organization's tenants, or your own under Personal, then Shared with you: tenants you reach through a seat that none of your organizations owns. Tenants that belong to your other organizations are counted at the foot of the menu, with a link to switch.
A link to another organization's tenant still opens it. The page says which organization it belongs to and offers Switch to that organization. Opening a page never changes your active organization; only the switch does.
Create tenant makes the active organization the owner, or you under Personal. If you are not an owner of the active organization, the page offers to switch to Personal instead.
Transfer ownership
Only an owner can do this, and you must hold an owner membership in the organization that receives the tenant. If you have none, create one at www.udibo.com/organizations first.
When an organization owns the tenant, only an owner of that organization can transfer it out. Its admins manage the tenant day to day, but Danger zone offers them no transfer and says to ask one of the organization's owners. The management API refuses an admin's transfer with a 403.
Open Settings for the tenant. Danger zone is at the foot of the General tab.
Under Receiving organization, pick the organization.
Choose Transfer ownership, type the organization's name to confirm, and choose Transfer ownership again.
The organization becomes the owner and your own Owner seat is revoked in the same step, or the organization that owned it loses its Owner access. Any other seats, yours included, stay as they are.
Limits today
The page shows up to 100 seats. Past that, it says the list is incomplete rather than showing the rest.
Invitations go to existing Udibo accounts only. There is no invite that creates the account.
Access levels are fixed. Admin, Owner and Support cannot be edited; finer access comes only from roles defined by an organization that owns the tenant.
Next: see how access carries into the management API, or review what administrators did in the audit log.
Last verified 2026-10-28.