Bridge Authorization Model
Bridge uses a role-based authorization system.
In Bridge v1, roles such as “developer”, “researcher”, and “admin” authorized users to perform actions within the context of an app.
In Bridge v2, where an app can support multiple studies, these roles will be replaced with “study developer”, “study coordinator”, and “organizational administrator,” people who will only be able to operate on the studies they have permission to access.
The app-scoped roles will be phased out for external use as part of the v2 development roadmap.
|Developer||App||Developers can currently change many aspects of an app's configuration for functionality such as authentication and server-supported app configuration. This role currently spans all studies and is app-scoped.|
|Researcher||App||A researcher can see all accounts in an app, including all study participants, along with their enrollment and consent records. This role currently spans all studies and is app-scoped.|
|Admin||App||An admin can use any API within the context of an individual app. In general, only Sage employees hold this role, but it can be granted to partners for specific apps.|
|Organization Administrator||Organization||An organization administrator can create, edit, and delete other administrative accounts within their organization. However, only admins can change the studies that an organization sponsors.|
|Study Coordinator||Study||A study coordinator can see participants in the studies that are sponsored by their organization. They can create, enroll and withdraw participants, and see their personally-identifying information.|
|Study Developer||Study||A study developer can change the configuration of any study in Bridge that is sponsored by their organization. This includes elements such as the consent, study protocol, and scheduling for the study.|
Administrative accounts in the Bridge system are scoped to an app and are members of an organization (this can be an institution, a team, or any other set of collaborators who are working together on a study). Members of an organization are granted access to one or more studies through the organization‘s sponsorship of those studies. Partners will be added to the Bridge platform with an initial organizational administrator who can manage further accounts in their organization through account and organization APIs.
Organization admins have a set of Account APIs for creating administrative accounts. These accounts are scoped to their organization and cannot be re-assigned. The members of an organization can be enumerated through a search API.
However if an account already exists, it can be associated to an organization through the add member and remove member APIs (only admins can move an account from one organization to another after it has been assigned). An API exists to return administrative users who are currently unassigned to an organization in order to find such accounts..
All of these APIs are tagged as a group of APIs that are available to organization administrators in our Swagger API definition.
Organizations can sponsor one or more studies, giving all members of an organization access to those studies (depending on their roles). There is an API to list an organization’s sponsored studies, and study developers can create new studies that are sponsored by their organization. Only admins can change the study sponsorships of an organization through APIs to sponsor the study or to stop sponsoring the study.