Integrations
This page explains which systems Fisar can currently connect with, which systems need supplier input and which areas are not currently part of the standard onboarding process.
Most customers should begin onboarding with Microsoft 365 or Google Workspace. Other integrations can then be reviewed once access has been requested. .
Core Supported Integrations
These are the main integration routes customers can usually begin with during onboarding.
| Integration | Customer Action |
|---|---|
| Microsoft 365 / Microsoft Graph | Use Single Sign On and provide tenant admin consent where required. Exact data scope depends on tenant setup, licensing, retention and permissions granted. |
| Google Education Suite / Google Workspace | Use Single Sign On and provide the required Google Workspace admin permissions. Exact data scope depends on Google admin control and permissions granted. |
Additional Integrations - Becoming Standardised
These integrations currently require supplier approval and API documentation before Fisar can move forward integrating.
| Integration | Customer Action |
|---|---|
| Access Evo / Access Education Finance | Confirm the exact product name/version and ask Access support to enable or provide API documentation and credentials where available. |
| Arbor | Contact Arbor or use the Arbor Developer Portal route, asking for third-party API access for Fisar SAR processing. |
| FMS / SIMS Finance | Ask ESS/SIMS support whether FMS data can be accessed through an approved API or export route for SAR processing. |
| iFinance | Provide the full supplier/product name, version, hosting details and support/account manager contact so Fisar can assess the correct route. |
| iSAMS / IRIS Ed:gen | Ask the iSAMS administrator to request API/developer access for Fisar and confirm which modules or data sets can be exposed. |
| iTrent | Ask the MHR/iTrent account manager for API documentation and the third-party access route for SAR processing. |
| Microsoft Windows Server | Involve customer IT and provide server architecture, access method, sample paths, AD/LDAP details, permissions model and remote access/security requirements. |
| ParentPay | Contact ParentPay support/account manager and request API or export documentation for SAR processing. |
| SAMpeople | Ask SAMpeople support/account manager for API documentation, partner access requirements and the third-party data-sharing process. |
| SIMS / ESS SIMS | Ask ESS SIMS what API route is available for SAR discovery and whether Fisar can be approved as an integration partner. |
| SOCS | Email SOCS support asking for third-party API or export documentation for SAR discovery. |
| WisePay | Ask WisePay/Eduspot support whether API or export access is available for SAR processing and what data fields can be provided. |
Future Or Not Currently Supported
These areas are not currently standard onboarding integrations. They may still be worth discussing, but they cannot be promised as part of the normal setup process.
| Integration | Customer Action |
|---|---|
| CPOMS | Contact CPOMS and ask for Fisar to be considered for integration access or added to a future integration request list. |
| Hikvision Central / HikCentral CCTV | Ask Hikvision or the customer’s CCTV installer/integrator for OpenAPI documentation and export options. Fisar should treat CCTV video retrieval and redaction as a future capability, not a standard integration. |
Supplier Contact Summary
| Integration | Suggested Contact Route |
|---|---|
| Access Evo / Access Education Finance | Access support/account manager or Access developer documentation |
| Arbor | api@arbor-education.com / Arbor Developer Portal |
| CPOMS | CPOMS support/account manager or CPOMS “Become a Partner” route |
| FMS / SIMS Finance | ESS SIMS / FMS support contact via customer portal |
| Google Workspace | Google Workspace Super Admin / Google Cloud project owner |
| Hikvision Central / HikCentral CCTV | Hikvision TPP Portal / customer CCTV installer or integrator |
| iFinance | Customer finance system owner / vendor account manager |
| iSAMS / IRIS Ed:gen | support@isams.com / iSAMS Partner Support / iSAMS Developer Portal |
| iTrent | MHR/iTrent account manager or support portal |
| Microsoft 365 / Microsoft Graph | Microsoft tenant administrator / Microsoft Entra admin |
| Microsoft Windows Server | Customer IT/network administrator |
| ParentPay | ParentPay support/account manager |
| SAMpeople | SAMpeople support/account manager |
| SIMS / ESS SIMS | ESS SIMS support, partner or integrator route |
| SOCS | support@miSOCS.com / SOCS support |
| WisePay | WisePay/Eduspot support or customer account manager |
What Customers Should Expect
Start With Core Access
Fisar usually begins onboarding with Microsoft 365 or Google Workspace so the customer can access the system and build momentum early.
Prioritise Additional Systems
The customer and Fisar should agree which additional systems matter most for SAR discovery.
Request Supplier Information
For non-core systems, the customer may need to contact their supplier and request API access, export options or integration documentation.
Review The Supplier Response
Fisar reviews the information provided and confirms whether the system can be connected directly, handled through export or planned for a later phase.
Important Notes
-
A system being listed here does not mean it is automatically available.
-
Supplier approval and API access are often outside Fisar’s direct control.
-
Some systems may require a manual export route rather than a direct integration.
-
Microsoft 365 and Google Workspace should usually be connected first.
-
Other integrations should be scoped after the customer has completed onboarding and identified their priority systems.\
Simple Rule
If a system is not Microsoft 365 or Google Workspace, treat it as something to scope before promising.
Fisar can guide the process, but customer permissions, supplier approval and API access will often determine what is possible.