> ## Documentation Index
> Fetch the complete documentation index at: https://signalschools.co.uk/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Arbor Data Processing

> Understand what Signal imports from Arbor, which fields are required, and how one-way MIS sync works.

This page explains what Signal imports from Arbor, how the data is used, and how to answer common DPIA and due-diligence questions.

<Note>
  This guidance covers the standard Arbor integration. For setup instructions, see [MIS Integration](/docs/getting-started/mis-integration).
</Note>

## Data flow direction

Signal's Arbor integration is **one-way (read-only)**:

* Data is read from Arbor into Signal.
* Signal does **not** write records back to Arbor.

## What data is imported from Arbor

### Students

* Arbor student ID
* First and last name (prefers Arbor preferred name fields when available)
* Date of birth
* UPN (Unique Pupil Number)
* Year group
* Registration form
* Admission date
* Leaving date
* Gender
* Ethnicity
* Religion
* Address and postcode
* Pupil premium flag
* In-care status
* SEN status
* Profile photo URL (if available)

### Contacts and guardians

* Arbor contact ID
* First and last name
* Relationship to student
* Email address
* Phone number
* Parental responsibility flag
* Authorised collection flag
* Contact priority

### Staff

* Arbor staff ID
* First and last name
* Email addresses
* Job title
* Active status
* Registration form tutor memberships

### Attendance

* Attendance record ID
* Student ID
* Date
* Session (morning/afternoon)
* Attendance mark code
* Attendance note
* Present / authorised absence / unauthorised absence flags

### School closures

* Academic holiday start date
* Academic holiday end date
* Holiday label

## Mandatory and optional fields

For student imports:

* **Required**: Arbor student ID and a valid student name.
* **Optional**: All other student fields are imported when present in Arbor.

For other record types (contacts, staff, attendance, closures), Signal imports available values from Arbor and applies validation where needed.

## Data minimisation

Signal applies data minimisation by importing a predefined set of fields needed for safeguarding workflows.

* Field-level import toggles are **not** currently configurable in-product.
* Schools can apply additional minimisation through Arbor permissions (least privilege).
* Disconnecting the MIS integration stops future syncs.

## Special category and safeguarding-related data

Depending on what exists in Arbor and what your school uses, the standard import can include safeguarding-relevant data such as:

* SEN status
* In-care status
* Attendance marks and notes
* Demographic data such as ethnicity and religion

Safeguarding incidents, actions, and case notes are created and managed within Signal.

## Related pages

* [MIS Integration](/docs/getting-started/mis-integration)
* [Bromcom Data Processing](/docs/mis-integration/bromcom)
* [Wonde Data Processing](/docs/mis-integration/wonde)