Inclusion Studio for IT and systems teams

IT and systems teams are asked to approve tools that touch learner data, with limited time and often limited information from suppliers. This page states the architecture plainly, including what is not decided or finished, so you can judge fit early.

What does an IT lead’s day look like?

You manage accounts, devices, networks, MIS links and licences, and field support calls. A new learner support tool means questions on sign-in, integration, data location, browser support, admin burden and what happens when it breaks. You want straight answers and a named list of third parties.

What do IT teams need?

• The architecture and the vendors involved.
• How people sign in and how access is removed.
• Where data and files are stored.
• What integrations exist and what they require.
• Browser and accessibility expectations.
• Honest status on security testing and certification.

What is the architecture?

Services other than the database may process data outside the UK. We do not claim UK-only or fully UK-hosted operation. Each service is to be documented and assessed before real learner data is used. See where data is processed and subprocessors.

How do sign-in and access work?

Clerk handles sign-in, sessions and multi-factor authentication. Our application and database hold the tenant, learner, relationship and field permissions. Clerk organisations map to internal tenant IDs, and a client-supplied organisation ID is never trusted without server verification. Clerk is meant to hold only minimal identity data, never diagnoses, SEND details or case notes. Privileged accounts and staff with sensitive access are intended to require MFA.

On single sign-on, the accurate statement is organisation sign-in where supported by the chosen plan. We make no claim beyond that. If you need a specific identity provider, protocol or provisioning method, raise it early so we can verify it rather than assume it. We also do not want revoked access to depend on a delayed notification, which is a design requirement for the production build.

How are permissions enforced?

On the server, by organisation, relationship and field, for every request, including files, search, exports and AI. Hiding a button is never the safeguard. Tests for cross-tenant access denial, sensitive-field and file access are part of the planned release gates. See permissions and roles and security.

How are files handled?

Files go to a private store and are streamed only to authorised users after a server-side check, with private, no-store caching headers. A guessed link or storage path is not enough to fetch a file. Untrusted uploads are quarantined until scanned. The scanning provider has not yet been chosen. Database and document storage are separate recovery domains, and restore tests for both are a pre-pilot requirement, not a completed fact. See documents.

What about integrations and imports?

CSV import and export come first. Any connector will be chosen from real pilot demand, and each installation needs granted scopes, source ownership, mapping, reconciliation and revocation. We do not claim universal native integration with MIS or learner record systems. See imports and integrations. Funding returns such as the individualised learner record stay with your MIS.

What about accessibility and browsers?

The target is WCAG 2.2 AA, with manual assistive technology checks for critical journeys still to come. Automated checks alone are not sufficient. See accessibility features and the accessibility statement.

What is the AI position?

AI is optional, uses a provider adapter, and is human-reviewed. The adapter targets Gemini on Google Cloud Vertex AI, called directly rather than through a gateway, and it has been exercised with synthetic data only in a preview environment. The live application uses a mock, and no real learner data has been sent to any AI provider. See AI principles.

What is the current status?

Inclusion Studio is pre-pilot. The production application is in development on synthetic data, with separate development, preview and production environments planned. There is no certification, such as Cyber Essentials or ISO 27001, and independent security review is a gate before real data. See the assurance roadmap. Questions are welcome via contact. For the privacy detail, see data protection officers.