Integrations

Full Fabric connects with external systems through built-in integrations and the public API. Staff set up most integrations under Settings → Other integrations; the Microsoft connection sits under Settings → Microsoft integrations, and Google and LinkedIn sign-in under Settings → Access & security → Authentication. Some integrations only appear once Full Fabric has switched them on for your institution.

Admissions and CRM

  • UCAS: applications from UCAS Undergraduate and UCAS Conservatoires, with decisions sent back to UCAS
  • UCAS sync and troubleshooting: sync schedule, imported data and common problems
  • HubSpot: profiles to contacts, emails and files to the HubSpot timeline
  • HubSpot deals: journeys to deals through sync rules
  • Salesforce: profiles to Leads and journeys to Opportunities
  • Sync management: the report of sync runs and failures for HubSpot, Canvas and Outlook

Teaching and learning

  • BigBlueButton: live virtual classrooms with automatic attendance tracking and recordings
  • Canvas: courses, users and enrolments created in Canvas
  • Canvas grades and assignments: grades and assignments brought back from Canvas
  • Turnitin: similarity-checked assignments over LTI 1.3
  • Microsoft oAuth: the Microsoft Entra ID connection used by Outlook calendar sync and by staff connecting their Outlook mailbox
  • Outlook calendar sync: academic sessions in Outlook calendars and room mailboxes

Signatures and interviews

  • DocuSign: signed applications and letters
  • PandaDoc: signed applications
  • Kira: video interviews as an application step

Payments

Sign-in, website and messaging

Single sign-on with SAML, including Microsoft Entra ID, is covered in SSO / SAML.

Permissions

Configuring an integration for the whole institution (connecting the account, choosing what to sync, editing field mappings) is governed by a single feature, Global integrations (core.institutions.global_integration_settings). It covers HubSpot, Salesforce, Canvas, PandaDoc, UCAS, BigBlueButton and the inbound email log, and it opens the Settings area on its own: a role does not also need the institution settings permissions to manage integrations, and it gains nothing else from those permissions either. In the Settings navigation the same feature also shows the Microsoft integrations and Other integrations sections as a whole, and the Inbound email, Pusher and MessageBird links under Infrastructure; the other pages listed there (analytics, payments, Turnitin and so on) are protected by their own permissions, so a role may see a link to a page it cannot open or change. Email gateways have their own feature, Email gateways (core.institutions.settings_email_gateways_change): it shows the Infrastructure section with only the Email gateways link, and it is the only feature that opens those pages.

Action Who can do it
Connect, disconnect or configure an institution integration Staff with Global integrations
Connect a third-party account to your own profile (for example LinkedIn) Any user with User integrations (core.institutions.user_integration_settings)

Note: Students, applicants and other lifecycle users hold User integrations for their own profile only. Institution-wide integration settings are never available to them, even through that permission.

New institutions grant Global integrations to the staff::administrator role. Existing staff roles that held User integrations when the permission was introduced received Global integrations automatically; lifecycle roles did not. See Features & Permissions for how features are assigned to roles.

Every institution has a staff::it role holding Custom domain (core.institutions.settings_custom_domain_change), Email gateways (core.institutions.settings_email_gateways_change) and read access to the institution settings (core.institutions.institutions_settings_access), for staff who set these up without access to profiles or applications. New institutions also grant Custom domain to staff::administrator. When the two permissions were introduced, roles holding the institution settings permission received Custom domain, and roles holding the retired advanced settings permission received Email gateways. Email gateway domains are stored trimmed and in lowercase; Amazon SES gateways accept ASCII domains only, while custom SMTP gateways also accept internationalised domains.