# Newsroom and TASS Data Integration ## How the Integration Works PortalHQ connects to TASS through the official TASS Web API, using API credentials the school configures in TASS. Each night, PortalHQ retrieves current students, their parents and carers, and staff from TASS. Newsroom by PortalHQ then refreshes its contact lists from that data, so families and staff who join or leave TASS flow through to mailing lists automatically, with no manual uploads required. Audiences can be built from any of the fields listed below (for example, all parents of Year 7 boarders, or all teaching staff), and those lists remain current as TASS records change. | Step | Frequency | What happens | |---|---|---| | TASS to PortalHQ | Nightly, around 1:00 am AEST | Current students, parents and carers, and staff are read from TASS and updated in PortalHQ. | | PortalHQ to Newsroom by PortalHQ contacts | Nightly | Newsroom by PortalHQ contacts and dynamic mailing lists are refreshed from the synced records. Families and staff who have left are removed. | ## Current Families (Parents and Carers) Parent and carer details are drawn from each current student's Communication Rules in TASS (API method getCommunicationRulesDetails). PortalHQ reads the Correspondence address, as well as the separate addresses used for split families (labelled Parent 1/Mother, Parent 2/Father, Parent/Carer 1, Parent/Carer 2 and similar), so that both households in a separated family are included. Only parents linked to at least one current student are included. When a family's last child leaves the school, that family is removed from the current parent audience automatically. ##### Fields retrieved for each parent or carer | PortalHQ field | Source in TASS | Notes | |---|---|---| | First name | Communication address: mother / father first name (m_first_name, f_first_name) | | | Surname | Communication address: mother / father surname (m_surname, f_surname) | | | Email address | Communication address: email and email 2 | Where both parents share one email field separated by a semicolon, each parent receives their own contact. | | Title | Communication address: salutation | | | Mobile phone | Communication address: mobile phone 1 and 2 | | | SMS permission | Communication address: SMS flags 1 and 2 | | | Relationship to student | Address description (Mother / Father, Parent/Carer 1 / 2) | | | Family code | Communication address: parent code | Links the parent to their children. | | Person number | Communication address: mother / father person number | Used to match the same parent on every sync. | | Deceased | Communication address: mother / father deceased flags | A deceased parent is never added as a contact. | ##### Fields inherited from their children (for targeting) | PortalHQ field | Source | |---|---| | Year level(s) | Each current child's year group | | House(s) | Each current child's house | | Campus(es) | Each current child's campus | | Form class(es) | Each current child's form class | | Boarding parent | Whether any current child is a boarder | ## Current Students Student details are drawn from the TASS current student record (API method getStudentsDetails). Optionally, students enrolled for a future start date can be brought in a set number of days before they commence, based on their date of entry. | PortalHQ field | Source in TASS | |---|---| | First name | General details: first name | | Preferred name | General details: preferred name | | Surname | General details: surname | | Student code | General details: student code | | Alternate ID | General details: alternate ID | | Gender | General details: gender | | Family code | General details: parent code (links the student to their parents) | | Next year indicator | General details: next year indicator | | Email address | School details: email address | | Year group | School details: year group | | Entry year group | School details: entry year group | | House | School details: house | | Campus | School details: campus | | Form class | School details: form class | | PC / tutor group | School details: PC tutor group | | Boarder | School details: boarder | | Lives with | Other school details: lives with | | Bus / excursions | Other school details: bus excursions | ## Staff Staff records are drawn from two TASS modules, depending on which the school uses. Teaching staff are drawn from TASS Learning Management (API method getTeachers). All employees, teaching and non-teaching, are drawn from TASS Payroll/HR (API method getEmployeesDetails). Staff without a school email address in TASS are skipped, and staff with a termination date are not added. Individual staff members can also be excluded from mailing lists within PortalHQ. | PortalHQ field | TASS Learning Management (teachers) | TASS Payroll/HR (all employees) | |---|---|---| | First name | First name | First name | | Preferred name | Preferred name | Preferred name | | Surname | Surname | Surname | | Email address | School email address | School email | | Employee code | Employee code | Employee code | | Mobile phone | Not provided | Mobile phone | | Teacher code and name | Teacher code, teacher name | Not provided | | Department(s) | Department | Not provided | | Teaching staff | Yes, everyone in this feed | No | ## Alumni Alumni are not retrieved from TASS by the automatic sync, which reads current students, families and staff only. Instead, alumni are loaded into Newsroom by PortalHQ from a spreadsheet export, and each contact is tagged as alumni with a Class Of year so that cohorts can be targeted (for example, a Class of 2016 reunion). The import can be repeated whenever the school's alumni records are updated. Schools that maintain alumni records in another system, such as a CRM or foundation database, can also push contacts into Newsroom by PortalHQ through the PortalHQ API. | Newsroom by PortalHQ field | Spreadsheet column | |---|---| | First name | Given name | | Surname | Surname | | Email address | Email (rows without an email are skipped) | | Class Of | Graduating year | | Is Alumni | Set automatically on import | ## Privacy and Preferences - Newsroom by PortalHQ only reads contact data from TASS. It never writes contact details back to TASS. - Contacts who unsubscribe in Newsroom by PortalHQ remain unsubscribed. A subsequent sync does not re-subscribe them. - Every email sent from Newsroom by PortalHQ includes an unsubscribe link. ## Enquiries For any queries regarding this integration, please contact TeamHQ at [support@teamhq.com.au](mailto:support@teamhq.com.au) or +61 2 8387 7321.