Appearance
Somebody is not connected, or is connected to the wrong thing
A parent, teacher or member of school staff has no account against their record, or has one that belongs to somebody else, or has asked to be connected to a lesson and nothing has happened. Two different things are at work - the account a person signs in with, and a request to be joined to a particular child's lesson - and they are mended in different places.
Step 1 of 10
Two different questions, and it is worth knowing which you have
"Can they sign in at all?" is about their account, and lives on their own record, on the Identity tab. "Are they joined to this child's lesson?" is a connection request, and lives in Tasks. Somebody can have a perfectly good account and no connection, or a connection waiting while they have no account yet, so start by deciding which of the two you are being told about.
Customers still call the account a Schooble account and the guide follows suit, because that is what the sign-in itself is called. What Xperios holds is a Paritor Identity, and the logins - Schooble, Google, Microsoft, Apple, a passkey - hang off it.
Use the arrow keys to move between steps.
Why this one is worth knowing
Almost every call in this area is one of two questions wearing the same words. "They are not connected" can mean they have no account to sign in with, or it can mean they have an account and are not joined to a particular child. The first lives on the Identity tab of their own record; the second lives in Tasks, Connection Requests. Deciding which before you start saves most of the work.
The single most useful fact on the second half is that a connection request is waiting for the teacher, not for you. The office cannot approve one. That is why the list grows, why nothing you do in Xperios moves it along, and why the only button there is Delete — which is for the ones that will never be answered, and the teacher shown as has left is how you spot them.
On the first half, the thing worth remembering is that an account found against another contact is not an error to work around. It is the same person entered twice, and merging the records is the fix. Attaching the account to the second copy would just split their history down the middle.
The same ground, as reference
- Identity — the tab itself, and every action on it
- A parent cannot sign in — when they have an account and still cannot get in
- A parent cannot see their child on the Portal — connected, signed in, and the child still missing
- Two records for the same person — merging, which is where an account on the wrong contact leads
- A member of staff cannot get in, or cannot change anything — the account question for staff, and the rights that follow it
