Connect
Community management — organisations, memberships, federation
What it does
The community layer on top of IAM. Organisations, memberships, role assignments, federated sign-on across twins. The basis for contributor programmes, partner directories, and customer communities. Inherits IAM grants, so every membership decision is auditable in the commitlog.
Connect is the layer where individuals become a community: an organisation has members, members have roles, roles carry IAM-granted capabilities. The Forus cooperative network, contributor programmes, partner directories, and customer-account hierarchies all run on Connect — same primitives across every twin.
Key features
- Organisations, memberships, role assignments
- Federated sign-on across IOBOXX twins
- Contributor and partner directories on the same substrate
How it works
Connect sits on top of IAM and the Object Store. Organisations are typed objects; memberships are typed edges with role attributes; sign-on is federated through the IAM tier. Cross-twin membership lookups are gated by the same capability-grant model used for any other memory walk.
- IAM — the identity primitive Connect inherits.
- Authorization architecture — capability grants for cross-twin membership.
- Mycelium — how sovereign twins compose into a federated community.
Try it
Open the contributor onboarding flow to see Connect at work — registering, joining an organisation, taking on a role.