Security & Compliance

This page summarises the security controls Full Fabric applies to every institution, for staff and for IT and data protection reviewers. Each section links to the page with full detail.

At a Glance

Area What Full Fabric does Read more
Tenant isolation Each institution has its own database; every request is tied to one institution Infrastructure & Isolation
Encryption in transit The platform is served over HTTPS; session cookies are only sent over encrypted connections Below
Authentication Password policy, failed sign-in protection, SMS two-factor, SAML single sign-on Authentication
Access control Roles and features, data access scopes, field-level permissions Identity & Auth
API access Expiring, revocable tokens with optional IP restrictions API Tokens
Audit trail Change history on records, per staff member and per API token Below
File uploads Virus scanning, private storage, downloads for signed-in users Below
Personal data Delete and Forget (right to erasure), consent records, policy acceptance Below

Tenant Isolation

Every institution is a separate tenant with its own database. A request is matched to one institution by its web address before any data is read, and user accounts, API tokens and background work all belong to a single institution. Sandboxes are further separate databases. See Infrastructure & Isolation.

Encryption

In transit

  • Full Fabric is served over HTTPS (TLS) on both its own addresses and custom domains.
  • Session cookies are marked Secure and HttpOnly: browsers send them only over encrypted connections, and scripts on the page cannot read them. See Sessions & Tokens.
  • A custom domain uses either a certificate managed and renewed by Full Fabric or one the institution uploads. See Custom Domains.

Sensitive values

  • When a profile is forgotten, its original personal data is encrypted with a key unique to that profile before being replaced with anonymous values. See Profile Operations.
  • Credentials an institution stores for third-party services, such as UCAS scheme passwords, are stored encrypted.

Authentication

Sign-in protections are described in full in Authentication. In summary:

  • Password policy: length, character rules, strength, lifetime and history, configured per institution.
  • Failed sign-in protection: repeated wrong passwords slow down further attempts. The delay applies to the combination of account and network address, so someone guessing from one place cannot lock the real user out from elsewhere. A separate limit across all addresses caps the total number of failed attempts on one account.
  • Two-factor authentication by SMS, which an institution can turn on.
  • Single sign-on with SAML 2.0. See SSO / SAML.
  • Session timeout, configurable per institution. See Sessions & Tokens.
  • Captcha on self-service account creation.

The staff list offers a reset of a staff member's two-factor setup, for users with that permission. See Managing Users.

Access Control

Inside an institution, every page and action checks three things: that the module is enabled, that the user's role holds the feature, and that the specific record allows the action.

Control Limits Read more
Roles and features Which areas and actions a user can use Features & Permissions
Data access scopes Which programmes, classes and courses a staff member can see Data Access Scopes
Schema permissions Which fields a user can view or edit Schema Permissions
Access windows The dates between which an account can sign in Managing Users

Applicants, students and other portal users see only their own records. Web forms in the app are protected against cross-site request forgery.

API Access

Integrations use API tokens rather than user passwords:

  • Tokens can be given an expiry date, suspended and revoked at any time.
  • Each token reaches only the endpoints its features allow.
  • Under IP restrictions, a token can be limited to a list of IPv4 addresses or CIDR ranges, one per line. Requests from any other address are refused. An empty list allows any address.
  • The token list shows each token's Last Activity, and the API Tokens page has an Activity tab.

See API Tokens.

Audit Trail

Full Fabric records who changed what, and when:

Where What staff see
Records An Activity history on applications and other records, with User, Action, Date and Changes
Staff members View audit trail in the staff list shows every change one staff member made, filterable by action, record type and date
API tokens The Activity tab and Last Activity column on the API Tokens page

Viewing a staff member's audit trail needs Access to audit logs for platform activities and changes (core.core.auditing_access).

File Uploads

  • Files people upload, such as application documents, are scanned for viruses before they are stored. An infected file is rejected.
  • Uploaded documents are kept in private storage. Downloading one requires signing in; a download link opened while signed out returns to the file after sign-in.

Personal Data and Privacy

Delete and Forget

Full Fabric offers two ways to remove a person:

  • Delete marks the profile as deleted, unsubscribes it from communications and ends its sessions. Its data is kept.
  • Forget supports the right to erasure: personal data is encrypted and replaced with anonymous placeholders.

Both work on one profile or in bulk. See Profile Operations.

Institutions publish a Privacy Policy, Marketing Policy and Cookie Policy. Full Fabric records when and where each person accepted them: on the website, when creating an account, from an email, when submitting a form, or when staff added the profile with consent from another source. People can change their privacy policy agreement later, and segments can filter on consent. See Segments.

Search history

The text of global searches is kept for 90 days, then deleted automatically.

Data Location and Ownership

Each institution's data stays in its own database and its own data warehouse. The institution controls its users, roles and integrations, and can export its data from lists and through the Public API.

Note: This page covers how the product behaves. Certifications, subprocessors, data processing agreements, hosting region, backups and incident response are outside its scope.