Skip to main content
This page is organised by symptom, not by cause: look for the sentence that describes what you can see on your screen. Each symptom answers the same pair of questions — is this even a fault, and what do you do next. It is worth starting with one rule, because it explains most reports:
A blank in Zebrania almost never means “something broke”. It means “nothing has arrived here yet”. The app deliberately does not distinguish “there is no data” from “you have no access to it” — because that distinction would itself give away something about somebody else’s data. So before you call something a fault, check whether the step that was supposed to produce that data actually happened.
By far the most common situation, and it is not a fault. A sign-in link is single-use: it stops working once used, and every fresh request invalidates the previous one. If several messages are sitting in your inbox and you click an older one, you will see “This link has expired or was already used. Request a new one below.” This whole family of cases — with the table of messages, the list of places to check in your inbox, and the school-mail-filter trap — is written up in Getting started, under The link expired, or you clicked an old link and The email never arrived. We do not repeat it here. If this is about a link to a single event rather than about signing in — that is, you see the heading “This booking link doesn’t work” — the right page is Access from a link, without signing in.

​
I cannot see my child

First work out which of the two lists they are missing from, because these are quite different situations:
That last row is the most common misunderstanding between two parents of the same child. The app actively tries to prevent it with the message “This child is already enrolled by another parent. Ask them to send you a guardian invitation instead of enrolling again.” If you see it, that is not a refusal — it is a hint to join the existing record rather than duplicate it.

​
I joined, but I am still waiting for approval

Enrolling a child in a class is not approved automatically. It goes to a person, who checks the PIN — the last 4 digits of the child’s PESEL — against the school’s records. Until then the child shows Pending. The decision is made by that class’s homeroom teacher, and also by the school office or a school administrator. There is no stated deadline, because it is done by hand — it can take until the school’s next working day. What to do: nothing, for the first day or two. If it waits noticeably longer, remind the homeroom teacher directly — a request does not expire on its own, but nobody is nudged about it either. The same applies to teachers joining a school: the request waits for whoever runs the school. That is covered in Joining a school and class.
Rejected is not a fault and cannot be undone by clicking. It usually means the PIN did not match the school’s records. Contact the homeroom teacher — normally it is enough to enrol again with the correct PIN.

​
The slot I wanted is gone

Also not a fault. Slots are shared by every parent in the class, and when booking opens many people click in the same second. The click that arrived first wins — and the tile may well have looked free a fraction of a second earlier. When you lose that race, a “Conflict” bar appears above the grid, with a technical description of the rejection underneath it, in English and with a slot number. You do not need to decipher it — it always means the same thing: that slot is already taken and was not assigned to you. What to do: close the bar and pick another time. Nothing was written “half way” — either you have a slot or you do not. The full account of the grid and its labels is in Booking a meeting. A tile you cannot click has one of several explanations, and they are worth telling apart, because only the first is about somebody else’s booking:

​
The class is empty — teacher’s view

If you open a class list and see a sentence like “Nobody from this class is visible, or you do not have access to this list.”, the “or” is deliberate. The app does not say whether the class is empty or whether you lack access. The most common cause is not a fault: teaching in a class does not by itself grant sight of its statements. Access belongs to that specific class’s homeroom teacher and to the people who run the school’s affairs. If you expect pupils there, check with administration whether you are assigned as the homeroom teacher. The second cause is not a fault either: some lists are statement-only lists — health, after-school care and activities hold a row only for a child whose parent filed something. An empty health list means “nobody reported anything”, not “the class is healthy”. This is set out in Class views and printouts.

​
My meetings are missing from my calendar

A subscribed calendar is a separate channel with its own reasons for being empty — an event not yet published, an event with no date set, or simply a refresh delay on Google’s or Apple’s side. Every case is collected in a table in Notifications and calendar.
If you can see meetings in the app but the other guardian has an empty calendar despite accepting their invitation correctly — check first that the child’s class enrolment is Approved. While it sits at Pending, the calendar feed has nothing to show. If the enrolment is approved and the feed is still empty after a few hours, report it — see below.
Remember too that a reminder is not proof: the source of truth for whether you hold a slot is the My bookings list under Booking, not a message that did or did not arrive.

​
Something is broken — how to report it

If after all of the above it still looks like a fault, report it from inside the app. Zebrania has a built-in form for exactly this — the Report a problem button. The form is named after the button and has three fields and one send button: You send it with Send report and back out with Cancel. Once sent you will see “Thank you for your report!”.

​
Attach a screenshot

The form has an Add a screenshot button — and it is the single most useful thing you can attach. The screenshot is taken of whatever is on your screen at that moment, so report the problem while you are standing on the broken page, not after navigating away. On the screenshot you can also:
  • Highlight — outline the place you mean;
  • Hide — mask a part you would rather not send;
  • Remove — delete a mark you made.
A screenshot sends whatever is visible on it. If other children’s data is on screen — a class list, a health statement, phone numbers — use Hide to mask it before sending, or drop the image with Remove screenshot and describe the problem in words instead.

​
What to write in the description

A report attaches technical context by itself, so you do not need to give your browser or version. The only useful part is what the app cannot know:
  • What you were trying to do — “I wanted to book the 17:00 slot”.
  • What happened instead — the exact sentence from the screen, if there was one.
  • When — roughly what time, if it was not just now.
  • Whether it repeats — once, or every time.
What not to put in: your child’s PIN, a PESEL number, the contents of a health statement, or other parents’ details. None of it is needed to diagnose a fault.
If you cannot see a Report a problem button, do not hunt for it — write to whoever runs Zebrania at your school. A report from them lands in the same place.

​
School or technical support — who to write to

This distinction saves the most time, because most matters are not application faults and technical support cannot resolve them.
Zebrania runs no separate helpline or email address for parents. The two routes that genuinely exist are your school and the Report a problem button — and for most of the table above the school is the faster one, because it is the school that holds the data you are asking about.

​
What next