Get Started Setting Up Trust Framework

configure raidiam connect's trust framework and all underlying components to enable secure data sharing between organizations set up reference data reflecting your federation structure and needs, onboard organizations, and more prerequisites you contacted raidiam and a new ecosystem was created for your governing organization you provided raidiam with the security standard to be used in the ecosystem, including the fapi profile version and the certificate standard you provided raidiam with the registration framework docid\ q6si2ya2zeapvwb028 er of your choice oauth dynamic client registration (dcr) or openid federatio n you are a global administrator for the ecosystem you wish to set up model the trust framework to model the trust framework, you need to set up reference data docid 1va0dd53w2xgc28o4nxts customizable data sets used to make the platform reflect the different necessities of the federation for more information on how to reflect your ecosystem/federation needs, see the modeling ecosystems docid\ doeepqassfziwifctylnv article once set up, this data is broadcasted inside raidiam connect at the organization level and appears as options for a series of menus within the organization configuration manage authorisation domains docid\ tsyz9akqgamxzhlcro7 h define the domains the federation supports, for example, open energy, open banking, or different establish the authorization domains that encapsulate specific areas of data or functionality within the ecosystem add roles and permissions docid\ qjsrouudsq9ywmgymltyv set up permissions and access levels within the domain this includes descriptions, access scopes, and any metadata that will enable api communication for the institutions that have been granted the role manage authorities docid\ arib4iyphsouorbfdublv add a regulatory authority in charge of one or more domains these entities will provide the necessary access scopes for ecosystem functionality learn more about authorities authorities docid\ vzfabjd7vdppnyxyyaqkm onboard organizations add participants, which can act as both data providers docid\ apm ilivcfpfft1ld0puc and data receivers docid 0icz dap0cfxtlrhddxni , to enable data sharing upon the end user's consent during onboarding, organization administration will be delegated to the participant's employee team, you can onboard organizations in the two following ways onboard organisations docid\ d9lskvl2qzy7d7w9bwjhw recommended to get started onboard organisations docid\ d9lskvl2qzy7d7w9bwjhw recommended to onboard bigger batches of organizations delegate organization administration onboard organization administrators to delegate organization management further enable organization administrators to manage their organization metadata, and publish the organization's technical resources like authorization servers, apis, and more assign authorisation domains and roles to onboarded organisations assign the authorisation domains and roles you added above to each onboarded organisation enabling their technical resources to integrate with each other for example, in a case when an organisation needs to be able to call the centralized directory docid\ kt2uiavikzfzklbevp1 g apis, you need to assign a role that gives this organisation the privileges to get an access token using the appropriate scope, grant type, and more add global administrators if your ecosystem needs more global administrators than you requested from raidiam before setting up the ecosystem, you may manage administrators docid\ z xxy9ycmvkqjo1ymz6l6 n ext steps set up certification types define terms & conditions docid\ zeomqa7zogy f ub8p9 d configure domain user system docid\ nklcuhtnevownecq41qbq define the apis the data providers docid\ apm ilivcfpfft1ld0puc can publish for data receivers docid 0icz dap0cfxtlrhddxni to integrate with define whether the authorization servers, client applications, or apis, must be certified if yes, define what are the certifications required for each technical resource