Organization & teams

The Organization 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 section of the Organization view's Settings tab. There are four organization roles, from most to least access:

• Org Admin - manages the whole organization: every trial, team and member, roles and invites, and organization settings. Typically the account lead.
• Manager - creates teams and manages the teams they own - their members, settings, and the permissions each team grants. Does not have organization-wide control.
• Staff - least privilege. A Staff member acts only within the teams they're assigned to, and only up to the permissions those teams grant them. This is the default role for new SSO users.
• Viewer - read only, across the whole organization. A Viewer sees everything: patients, trials, calls and texts, the Inbox, agents, phones, teams and the Organization view, and can change nothing: no screening, no outreach, no edits, no exports. For people in your organization who need to see the account without acting on it.

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 an owner - the Manager who created it - plus its assigned members. Crucially, each team also grants a set of permissions to those members: viewing or editing trials and patients, placing prescreening calls, managing agents, and so on. The team owner configures those grants.

• Team owner - the Manager who created the team; manages its members, settings, and permission grants.
• Team member - anyone assigned to the team; can do exactly what the team grants, on that team's trials and patients.

To create a team, go to the Teams section of the Organization view and click New team. Give it a name, add members from your org, and set the permissions it grants. Teams can be deleted by their owner or an Org Admin.

Metrics

The Metrics tab of the Organization view reports how your organization is performing across every trial at once, broken down by the EHR each patient came from. A patient who was matched to three trials counts three times - the unit is a patient-trial pair, not a person.

Patients by EHR shows each status - Qualified, Possible candidates, Pending, Disqualified, Outreached, Enrolled - as initial → actual.Initial is what the matching engine concluded on its own; actualis where the patient ended up after your team's edits and findings. Three rates summarize each EHR:

• Qualified - qualified ÷ evaluated, counted after coordinator review, so EHRs are comparable at a glance.
• Corrected - how often review overturned the engine's verdict. A high rate means the engine reads that EHR's records poorly.
• No data - how often a criterion couldn't be judged from the record at all. This is usually the explanation behind a low qualified rate: a sparse EHR produces unknowns, not disqualifications.

Below the table, outreach is summarized org-wide: conversations, messages sent and received, reply rate, and average time to a reply.

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 Organization view's Settings tab:

1. 1

   Open SSO Tenant Mappings

   Scroll to the bottom of the Organization view's Settings tab. 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 organization role that new SSO users get when they first sign in. Staff is the right default for most clinical research teams - assign them to the appropriate teams afterward.
4. 4

   Save

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