Appearance
A member of staff cannot get in, or cannot change anything
Somebody new cannot reach Xperios, or somebody who has used it for years suddenly cannot save. There are three separate gates - a user record, a licence, and the rights their group gives them - and they fail in different ways, so the first job is working out which one you are looking at.
Step 1 of 8
A member of staff needs the User role before anything else
Being a contact is not being a user. Edit the person and the toolbar offers to make them one, and the User tab appears - that is where everything on this page lives. The tab says straight away whether they can actually sign in: where they cannot, it tells you so and offers Send User Invite, which emails them a link to set themselves up, and Get Connection Code for somebody joining by code instead.
Signing in and being allowed to do things are two different questions. The invite settles the first; the licence and the groups below settle the second, and somebody can easily have one without the other.
Use the arrow keys to move between steps.
Why this one is worth knowing
Three gates, and they fail in ways that look alike from a support call.
No user record and they cannot get in at all. No licence, or none left of that type, and the save that would have given them one is refused — so the failure lands on you while you are setting them up, not on them. A Manager licence and they get all the way in, see everything, and cannot save a thing. A group without the right and they are in, able to work, and one area is simply not there.
The one worth knowing about before it bites is the Manager licence, because it looks exactly like a permissions fault and is not one: everything is visible, nothing is saveable, and no amount of adding groups will change it. Look for the Read-only badge by their name first and you will save yourself an afternoon in the rights tree.
And when you do get into the rights tree, test with an ordinary account. Administrators pass every check, so testing as yourself tells you nothing about what anybody else can see.
The same ground, as reference
- User Groups — rights, how they are graded, and why an administrator is not tested against them
- Giving somebody a role — making a contact a user in the first place
- Identity — how somebody signs in, which is a separate question from what they may do
- A teacher cannot see or do something — the teaching side of the same question, where the answer is usually the schedule rather than a right
- A parent cannot sign in — the same distinction between the login and the record, from the family's side
