/

Ambitwin · source-available, not open source · © 2026 Nicolò Ghignatti

Identity & Access

Keywords on this page
WordMeaningExample
AccountOne person who can sign inLia
OrganizationA customer. The unit that keeps data apartnorthfield-university
Sub-organizationA part of an organization with its own accessphysics under Northfield
Membership“This person belongs here, with this role”Lia in Northfield, Standard User
RoleHow much a person may do inside one organizationStaff Member
Sign-in MethodHow an organization checks peopleIts own passwords, or the company login
PassStatement of who you are and your membershipsLia’s pass, valid for minutes
TenantSame as Organization: one customer, kept apart from the othersNorthfield and Acme are two tenants

Question: who are you, and what may you do? Kind: Supporting. Needs: nothing.

Comes first because every other domain needs to know who is asking.


In the real world

Lia studies at Northfield University and volunteers at a city museum. Both use Ambitwin.

So: a person is one thing, and their place inside an organization is another.


The model

classDiagram
    class Account {
        name
        email
    }
    class Membership {
        organization
        role
    }
    class Organization {
        name
        visibility
        signInMethod
    }
    Account "1" *-- "many" Membership
    Membership "many" ..> "1" Organization : by name
    Organization "1" *-- "many" Organization : sub-organizations

Roles

Three roles. Each can do everything the one below can.

Domain Administrator > Staff Member > Standard User
RoleCan
Standard UserSee buildings and live values, ask the assistant
Staff MemberAlso edit rooms, connect sensors, set room limits
Domain AdministratorAlso add buildings, onboard members, split the organization

Checking is one rule: your role must be at least the one needed.

The Platform Administrator is not on this list. They run the platform and hold no membership.


Rules

  1. One Account has at most one Membership per Organization. Joining again changes the role. It does not add a second one.
  2. An Organization’s name is unique and never changes. Everyone refers to it by that name.
  3. An administrator can give a role up to their own, never higher.
  4. Creating an Organization needs no human help: sign up, create, use.
  5. A taken name is refused, and nothing is created.
  6. An Organization using a company login takes no self-service joins. The company decides who is in.
  7. A hidden Organization does not show in search. To outsiders, it does not exist.

The pass

The main thing this domain gives to the others.

who:          lia@example.com
memberships:  northfield-university  Standard User
              city-museum            Staff Member
valid for:    a short time
issued by:    Identity & Access, and nobody else
sequenceDiagram
    participant L as Lia
    participant I as Identity & Access
    participant B as Building Management
    L->>I: sign in
    Note over I: find account and memberships
    I-->>L: pass
    L->>B: buildings of northfield-university, here is my pass
    Note over B: does the pass list northfield-university? yes
    B-->>L: Science Hall

Trade-off: if Lia loses a role, her pass still shows the old one until it expires. That is why a pass lives only for minutes.


Open questions