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

# Communicating with parents

> Ardoise in-app notifications.

<Note>This page concerns Ardoise School in the OHADA scope, subject to enabled modules and permissions. School, school accounting and payroll are not offered in Austria. Check local requirements; CountryConfig does not certify compliance.</Note>

## Automatic notifications

Ardoise automatically notifies parents of certain events: payment received, report card available, document generated (certificate, report card), unexcused absence, disciplinary measure, and fee due-date reminders.

## One channel: the Ardoise portal

These school notifications appear in the parent portal, with unread count and a link to the relevant record. This journey is not an SMS service. Transactional account/invitation emails and other integrations are separate flows; it does not mean Ardoise never uses an external service.

Parents see their notifications in their portal's notification centre, with an unread counter. Each notification links straight to what it is about (the report card, the payment, the document).

<Note>
  A notification can only reach a parent who has a portal account. A guardian without one receives nothing - create their access from the family record.
</Note>

## Reminders

Due-date reminders are produced by the `send_due_reminders` command, meant to run once a day from the school's own cron. It cannot produce duplicates: one invoice raises at most one reminder per day, enforced by the database, even if the command is run several times.

## School calendar: import CSV or XLSX

In the censeur calendar, select the school year and the calendar-import action. Use the offered Excel template or a CSV/XLSX containing date, kind and label. Use the template's accepted kinds (holiday or event) and the expected date format.

1. Select the file. The first upload is a preview without writes.
2. Map **Date**, **Kind** and **Label** to the exact column headers and refresh the preview after any change.
3. Review rows, flagged duplicates and numbered errors. Correct every conflict: an invalid row prevents the entire apply.
4. Apply only after a valid preview. The server revalidates and commits the file atomically with the configured audit record.
5. If the response is lost, preview the same file again: identical existing events are skipped without duplication; conflicting differences require correction.

<Note>
  This imports the school calendar, not every legacy dataset. General pupil, family, staff/tutor, opening-balance, booking and institute imports remain open. Encrypted school transfer is a separate targeted journey in [Pupils](/en/guide-utilisateur/eleves).
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.