Skip to main content
Everything you do in Zebrania as a parent starts with a child on your list. This page covers how to get one there, what happens when you enrol them in a class, and where the one genuinely confusing part of the product comes from.

​
Adding a child

Go to My children. Adding a child does not require a class code or any contact with the school — you can do it right away and name the school later. The app says so at the top of the page:
Add a child once, then assign them to a school whenever you have a class code. Editing a child here never changes an already-enrolled student.
In the Add a child form you give a first name, a last name, and a PIN — PESEL (last 4 digits). The PIN is not a password; it lets the homeroom teacher check that you are enrolling your own child: “PIN = last 4 digits of child’s PESEL. The teacher will verify identity.” Enter a different number of digits and you’ll see “PIN must be 4 digits”. Once added, the app confirms: “Added (name). You can assign them to a class below.” Until you have added anyone, the list reads “You haven’t added any children yet. Add one above to get started.” You can correct a child’s details at any time with Edit, saving with Save changes — the app confirms “Child details updated.” Any guardian linked to that child can edit them.

​
Enrolling a child in a class

A class needs a class code from the teacher. On the child’s row press Assign to a class, enter the code, and press Assign. The enrolment is not accepted on the spot. The app replies: “Assigned. The teacher will verify and approve the enrollment.” From then on it carries one of three states, shown next to the child: Where to get a code, and what to do when it does not work, is covered in Joining a school and class.

​
Child vs. student — two records, not one

This is the part that surprises people most often. It is worth a moment, because it explains nearly every “I corrected it and it is still wrong” question. Zebrania holds two separate records about the same person:
  • The child — on your My children list. It belongs to you. It exists on its own, with no school attached.
  • The student — in one specific class at one specific school. It belongs to the school.
At the moment you enrol them in a class, the school receives a copy of the child’s details: first name, last name and PIN are transcribed into a new student record. From that moment nothing links them live any more. It is a copy, not a window onto your data. One thing follows, spelled out on the My children page itself — “Editing a child here never changes an already-enrolled student”:
If you fix a typo in a surname on your list after the child is enrolled, the school will not see it. Fix it on your side, and additionally ask the homeroom teacher to correct the student record.
This can look like an oversight, but it is deliberate. Were it one record, your edit would silently rewrite the school’s documentation — and conversely, a teacher’s correction would change your own data. Two records mean each side owns what is theirs and nobody overwrites anybody. The same principle explains why one child can be a student in several places at once: each enrolment creates its own student record. If a child attends two schools, or moves mid-year, each holds its own copy and maintains it separately.

​
Several children, different classes and schools

One account covers all your children — you do not create a second account or switch profiles.
  • Add each child separately on the My children list.
  • Assign each with its own code to its own class. A code belongs to a class, not to a child.
  • Children can be in different classes, and even at different schools. Meeting bookings are then separate events — see Booking a meeting.
If the other parent has already enrolled this child, do not enrol them again — that creates a second, independent record. Ask that person for a guardian invitation: you join the existing record instead of duplicating it. The invitation is sent with the Invite a guardian button, and it is only available for a child whose enrolment is Approved.

​
Contact details

Contact details live on their own page — Contact details — and they belong to the student enrolled in a class, not to the child on your list. That is why, before you enrol a child anywhere, you’ll see: “You have no enrolled children yet. Once you enroll a child in a class, the form appears here.” The app explains what the school needs them for at the top of the page:
Your homeroom teacher needs a current phone number and email address for each child. Fill them in once, and in September confirming takes a single click.
You give a Phone and an Email address. The phone must be in international format — “E.164 format, e.g. +48123456789.” — that is, with the +48 prefix and no spaces or dashes. For each child you’ll see one of two states: After saving, the app confirms: “Contact details saved.”

​
Who can see them

You give contact details to the school the child is enrolled at — the homeroom teacher of that class, plus the people who run the school’s administrative side (secretary, administrator). Other parents cannot see them, and they are not published on any list. You give them separately for each child, even when the number is the same. A child enrolled at two schools has two student records, so you fill the details in at each.
Contact details are one of the declarations collected per child. The rest — consents, after-school care, pickup — are covered in Consents and statements. An empty entry is not a refusal: the app says so outright, “Nothing has been stated. This is not a refusal.”

​
What next