Organisations in Raidiam Connect: manage participants across any trust ecosystem
Onboard and manage the organisations that participate in your ecosystem or federation. An organisation is the primary entity on the Raidiam Connect platform — every user, application, certificate, and API resource belongs to one.
What is an organisation
An organisation represents a real business entity — a company, government body, or other legal entity — within a Trust Framework. Each organisation is linked to a unique registration number and serves as the container for all of the entity's technical resources on Raidiam Connect.
What an organisation does within the ecosystem is determined by the roles assigned to it through domains — not by a fixed type. The same organisation model supports Open Finance providers, enterprise partners, digital wallet operators, AI agent hosts, and any other participant category your ecosystem defines.
What an organisation contains
-
Applications — client applications (software statements) that access APIs or issue credentials on behalf of the organisation.
-
Authorisation servers — OAuth authorisation servers published by the organisation, enabling other participants to discover configuration, register clients, and obtain access tokens.
-
API resources — standardised API endpoints the organisation exposes to other ecosystem participants.
-
Certificates — X.509 digital certificates for mutual TLS, request signing, and encryption, issued by the ecosystem's Public Key Infrastructure or imported from an external CA.
-
Roles — ecosystem-specific roles that control which APIs the organisation can publish or consume, which scopes its applications can request, and how it is classified within the ecosystem.
-
Contacts — business, technical, billing, incident, and security contacts that other participants and administrators can look up.
How roles define what an organisation can do
Rather than splitting organisations into fixed categories, Raidiam Connect uses roles scoped to domains to govern capabilities. A Trust Framework Administrator assigns roles to each organisation, and those roles determine permissions, API access, and OAuth scopes.
A single organisation can hold multiple roles — for example, an insurance company might be an API provider in the Open Insurance domain and an API consumer in the Open Banking domain. For more detail, see Organisation roles and capabilities.
Use cases across ecosystems
Open Finance
Banks, insurers, pension funds, and payment institutions share user-permissioned financial data with authorised third-party providers. Provider organisations publish authorisation servers and APIs; consumer organisations register client applications and obtain certificates for secure access.
Enterprise data sharing
Organisations expose internal APIs to partners, suppliers, or customers within a private or consortium trust framework. Roles distinguish API publishers from API consumers, and the participant directory ensures that only accredited partners can discover and call those APIs.
Digital wallet ecosystems
Credential issuers (governments, universities, employers) publish signing keys and metadata. Wallet providers register wallet applications. Credential verifiers discover trusted issuers through the directory's trust infrastructure. All three participant types are modelled as organisations with appropriate roles.
AI agent ecosystems
Organisations register AI agents as applications with delegated credentials, enabling agents to call APIs and present attestations on behalf of the organisation. Roles and scopes control what each agent can access, and the participant directory provides discoverability and trust verification.
Regulated industries
Healthcare, energy, telecommunications, and government ecosystems use domain-specific roles and compliance requirements. The same organisation model accommodates sector-specific regulations while keeping the onboarding and lifecycle process consistent.
Next steps
-
Organisation roles and capabilities — understand how roles control what an organisation can do
-
Organisation contacts — register contact details for your organisation
-
Organisation statuses — learn about the Active and Withdrawn lifecycle states
-
How to onboard organisations — step-by-step onboarding instructions
-
Participant directory — the registry that manages all organisations and their resources
Roles and Capabilities
Understand how roles and domains control what an organisation can do — publish APIs, register clients, issue credentials, or consume data — in a Raidiam trust framework.
Contacts
Register business, technical, billing, incident, and security contacts for organisations in Raidiam Connect to enable communication between ecosystem participants.
Statuses
Learn how organisation statuses — Active and Withdrawn — control participant lifecycle, offboarding, and reinstatement in Raidiam Connect.