Team & organizations

The Team view is where org admins manage who has access to Bond Trials and what they can do. Each organization is a self-contained workspace — its own trials, patients, call history, and storage. Nothing is shared between organizations, even if the same person is a member of more than one.

Getting an organization

Organizations are provisioned by the Bond Trials team — you can't create one yourself from inside the app. To get your organization set up, contact Bond Trials and provide:

• Your organization's full legal name and a short slug (e.g. mass-general).
• Your preferred AWS data region (defaults to us-east-1 if not specified).
• Whether you want Google-based invites, enterprise SSO (Microsoft or Okta), or both.

Once your org is created, Bond will either send an initial invite link to your designated org owner, or configure your SSO tenant mapping so your team can sign in immediately with their existing corporate credentials — no invite needed in that case.

Members & roles

Org admins manage access from the Members tab in the Team view. There are five org-level roles, each scoped to a specific set of responsibilities:

• Owner — full access including billing and deleting the organization. Typically the account lead.
• Organization Admin — can manage members, teams, and workspace settings. Cannot delete the org.
• Research Coordinator — full trial and patient access, can place prescreening calls and manage agents. Cannot manage members or settings. This is the default role for new SSO users.
• Investigator — can view trials and patients and override eligibility verdicts. Cannot place calls, create trials, or manage members. Designed for PIs and sub-investigators who review eligibility decisions.
• Viewer — read-only access across all trials and patients. No actions. Designed for sponsor monitors, data managers, and executives.

To invite someone, click Invite member, enter their email, and select a role. They'll receive an email and land in your workspace as soon as they sign in with that address. To remove a member, use the remove action on their row — their active sessions are ended immediately.

Teams

Teams are an optional grouping layer inside an organization. They let you cluster coordinators, investigators, and other staff who work together on a related set of trials — useful when a larger organization runs multiple independent research programs and wants to keep those groups distinct.

Every team has its own member list and two internal roles:

• Team Admin — can manage the team's member list and settings within that team.
• Team Member — participates in the team. Their org-level role still governs what they can do in the platform.

To create a team, go to the Teams tab in the Team view and click New team. Give it a name, then add members from your org. Teams can be deleted by a Team Admin or Org Admin — the delete action appears in the team detail view for users with the right permissions.

SSO (Single Sign-On)

SSO lets your team sign in to Bond Trials using their existing corporate identity — Microsoft (Azure AD / Entra ID) or Okta — rather than creating a separate Google account or waiting for an individual invite. Once SSO is configured for your organization, any user your IT team grants access to in your identity provider can sign straight into Bond.

For end users: go to the Bond Trials login page and click Continue with Microsoft or Continue with Okta, depending on what your organization uses. Sign in with your normal corporate credentials. Bond will recognize your tenant and place you in the right workspace automatically — no invite code, no separate account needed.

For org owners — setting up the SSO tenant mapping: SSO only works after an org owner links your identity provider tenant to your Bond organization. This is a one-time setup done from the SSO Tenant Mappings panel at the bottom of the Team view:

1. 1

   Open SSO Tenant Mappings

   Scroll to the bottom of the Team view. The panel is visible to org owners only.
2. 2

   Click Add mapping

   Select your provider (Microsoft or Okta), then paste your tenant identifier. For Azure AD this is your Directory (tenant) ID — a GUID found in Azure Portal → Azure Active Directory → Overview. For Okta this is your Okta domain (e.g. acme.okta.com).
3. 3

   Set the default role

   Choose the org-level role that new SSO users will get when they first sign in. Research Coordinator is the right default for most clinical research teams.
4. 4

   Save

   Takes effect immediately. Anyone your IT team has already granted access to in your IdP can now sign into Bond.