Integrations
Which systems Fisar connects to today, which are in beta or coming, and how any other system gets scoped during onboarding.
There are two separate things people mean by "integrations", and it helps to keep them apart:
- Connectors built into the platform - available in Fisar right now, connected by you in a few clicks
- Other systems - scoped during onboarding, usually requiring supplier approval before anything can be built
Connectors available in the platform
These appear on the Integrations screen in your DPO dashboard.
| Connector | Status | Covers |
|---|---|---|
| MS365 | Live | Microsoft 365 - email, OneDrive, SharePoint, chats |
| Live | Google Drive API | |
| Bromcom | Beta | Bromcom school management system |
| Arbor | Beta | Arbor MIS (rest-v2, HTTP Basic Auth) |
| Integris | Upcoming | Integris education management platform |
| Slack | Upcoming | Slack workspace |
Connectors are added regularly. The Integrations screen in your dashboard is always the definitive list for your account - see Connecting Your Systems.
Upcoming means not yet available. Items marked upcoming cannot be connected today and should not be relied on when planning.
Start with Microsoft 365 or Google
Onboarding normally begins with whichever of these you use. Both authorise through single sign-on with your own administrator account, so they can usually be connected the same day and let you start running real requests immediately.
Everything else is scoped afterwards, once you know which systems actually matter for your requests.
Other systems
Any system without a built-in connector needs to be assessed individually. Whether it can be connected depends on the supplier - not on Fisar.
Systems customers commonly raise include MIS and finance platforms such as Access Evo, SIMS and FMS, iSAMS, iTrent, ParentPay, SAMpeople, SOCS and WisePay, safeguarding tools such as CPOMS, and file storage on Windows Server.
Listing a system here does not mean it is supported. It means it is a conversation worth having. Supplier approval and API availability are outside Fisar's control.
For each of these, the route is the same:
Agree priorities
Decide with Fisar which systems genuinely matter for your SARs. Most organisations need far fewer than they first assume.
Ask the supplier
Request API access, export options or integration documentation. See Requesting API Access for templates you can send.
Fisar reviews the response
Fisar assesses whether the system can be connected directly, handled by export, or planned for later.
Confirm the route
Allow 24-48 hours per integration once complete access information has been provided.
If a system cannot be connected
That is not the end of the road. You can still process the data.
Export the relevant documents, put them in a ZIP, and run them through Upload documents. They go through exactly the same redaction pipeline as connector-collected data.
This is the practical answer for most long-tail systems. Rather than waiting on a supplier, export and upload.
CCTV and video
Video redaction is a live capability - see Media SAR: Video. Direct integration with CCTV platforms such as HikCentral is a different matter and is not a standard onboarding integration.
In practice: export the footage, then process it through Process media.