Flags

assign flags to resources to categorise them distinguish different organisations, applications, and authorisation servers flags in raidiam connect are used as tags used to categorise technical resources within the platform created and managed by trust framework administrators (super users), flags are part of the system’s reference data and serve as labels to apply to different resources flags can be assigned to organisations applications authorisation servers super users or data administrators can create new flags using the platform's ui or apis the purpose of flags is to provide a flexible way to group, filter, and manage these entities within raidiam connect by tagging resources with specific flags, administrators can categorise and identify them more easily, organising resources logically across the platform assigning flags to authorisation server flags are defined by the following fields status indicates whether the flag is active or inactive for the participants type resource type with which the flag is associated organisation, application, or authorisation server value the flag value present in the ui and returned by connect apis id unique identifier of the flag once a flag is created in reference data, it is made available to be selected to the entire ecosystem anyone with a write access to that resource can interact with that flag examples of flags organization type bank payment service provider (psp) fintech regulatory body insurance provider compliance level psd2 compliant gdpr compliant open banking standard certified organization size enterprise sme startup