Project

General

Profile

MIS integrations: security and data protection FAQ

This page answers the questions school IT and data protection teams most often ask before connecting their management information system (MIS), such as iSAMS, to Potentiality. It sits alongside our Data Protection and Security Pack, which covers hosting, security controls, sub-processors and breach handling in full.

Some details depend on how your own site is set up: the exact fields, the permissions the connection needs, and what your administrators have chosen to show members. We confirm those for your site in writing on request.

Why connect the MIS at all?

Potentiality holds your community records: former pupils, current and former parents, and other supporters. Without a connection, keeping those records up to date means exporting spreadsheets from the MIS and uploading them by hand. Those files tend to be emailed between staff, saved on laptops and kept long after they are needed.

A read-only, least-privilege connection replaces that manual handling with one controlled feed that the school owns and can switch off at any time.

What does the connection access?

  • Only the data your site needs, typically pupil and parent/guardian contact details and the MIS's own identifier for each person. The exact list of fields for your site is agreed with you and can be seen at any time on the Database sync dashboard (see below).
  • Read-only. The connection never writes, changes or deletes anything in your MIS.
  • Least privilege. Your school creates the API credential in the MIS and decides its permissions. Grant only the permissions we list for your site. If your MIS can restrict a credential to particular IP addresses, ask us for ours.

Who owns the credential, and how is it revoked?

  • The credential belongs to your school. You can rotate or revoke it in your MIS at any time, and the sync stops straight away. Nothing else in your site depends on it, so revoking it is a complete rollback.
  • Please send it to us through a secure channel, not by email. We keep credentials out of emails, support tickets and source code, and replace them whenever you rotate them.

What is the MIS identifier (for example the iSAMS PersonGUID) used for?

Only as a matching key, so that each sync updates the right person instead of creating a duplicate. It is not shown to members and is not used for anything else.

Who can see imported records?

  • Your administrators, each limited to what their permissions allow, down to individual fields.
  • Named Potentiality support staff, only when supporting your site (see section 10 of the Security Pack for access from Australia).
  • Members see only what your site's directory and privacy settings allow. Your administrators control whether a group of records, such as former parents, appears in any member-facing area. We can confirm your site's settings in writing.

How do we know the sync is working, and what it changed?

Every site with an automatic sync has a Database sync dashboard, under Dashboards > Records and research > Database sync. It is shown to administrators with sync permission. It shows:

  • when the sync last checked in, and when it last brought in a change;
  • a status badge, so a stalled sync is visible within a day;
  • how many records and field values it changed over the last 30 days;
  • every field change, with the value before and after, downloadable as CSV;
  • records that are out of step with your MIS, and why;
  • the history of sync runs, and the mapping of MIS fields to Potentiality fields.

Where is the data stored?

For UK schools, in Amazon Web Services in London. The database is encrypted at rest, has no public internet access, and each client's data is held in its own tables, reached through a database account that can only access that client's tables. Backups are encrypted and kept in the same region. See sections 4, 5 and 8 of the Security Pack.

Is any data transferred outside the UK?

Your data stays hosted in London and is not copied to or stored elsewhere. Remote access from Australia for engineering or out-of-hours support is a restricted transfer under UK GDPR, covered by the UK IDTA or UK Addendum and a transfer risk assessment. See section 10 of the Security Pack.

How are imported records deleted?

  • Administrators can delete records individually or in bulk at any time.
  • At your request we will remove every record that came from your MIS.
  • A deleted record is removed from the live system immediately and drops out of encrypted backups as they expire, at most 3 months later.
  • At the end of a contract we delete your site and all its tables within 30 days of your written request.

What assurance do you provide as a supplier?

  • We act as your processor under UK GDPR, with Article 28 terms in our Service Agreement and a signed Data Processing Agreement available.
  • Weekly application scanning (OWASP ZAP) and independent security assessment. A summary is available under NDA.
  • A documented breach procedure, with notification to you within 48 hours.
  • We are happy to complete your own supplier security questionnaire.

How should the change be rolled out?

A sequence that fits a standard change-management process:

  1. Your IT team creates a read-only credential with only the permissions we list, plus an IP restriction if available, and shares it securely.
  2. We run the first sync with your team, and check the record counts, field mapping and a sample of records together on the Database sync dashboard.
  3. Once you are happy, the sync runs on its normal schedule and the dashboard shows its status from then on.
  4. Rollback at any point is revoking the credential. The dashboard lists every record the sync created or changed, so anything can be reviewed or reversed.

What about exports to third parties?

Any export to another organisation, for example a screening or mailing partner, is made by your own administrators from Potentiality and limited to the fields you choose. That third party has no access to your MIS or to Potentiality. As controller, your school decides whether the export is appropriate and covers it in its privacy notice and data protection assessment.

Related pages


sub-pages