Who may sign in

Three settings decide who can get as far as your school’s front door. They are separate screens because they are separate decisions, often taken by different people.

Your email domain

Admin → Domains, and Admin → Set-up to claim a new one.

Claiming a domain means adding a verification record to your DNS. Until that is verified, nobody can ask for an account using an address at your school – which is why it is the first thing to do and not the last.

The screen shows you what the change will affect before you make it: the counts and the switch are on one path, with the domain in the address, so there is no way to reach the button without having been shown what it does.

If a domain’s claim lapses, we can restore it – that one is on our side rather than yours, for the same reason connecting a MIS is.

Single sign-on

Admin → Single sign-on, and Admin → Set-up to register a provider.

Microsoft and MyLogin are both registered on the set-up screen, together with the domain, because a school establishing itself does all three in one sitting.

Once a provider is registered, its tile appears on the sign-in screen for anybody at your domain. Your staff can also be given a direct bookmark that goes straight to your school’s provider, which is worth putting in a briefing: it skips a screen for three hundred people.

A member of staff who already has a Ten Points login can join it to your provider rather than ending up with two ways in that do not know about each other.

The second factor floor

Admin → Second factor.

This is the level your school requires of everybody. Raising it does not lock anybody out: the next time somebody signs in, they are asked to enrol and given the screen to do it on.

Individual factors are enrolled by each person under Account → Security, which sits outside the administration section deliberately – whoever owes a factor must be able to enrol one whatever else they hold.

Why some actions ask for more than others

Reaching a class list and revealing a child’s sign-in secret are not the same act. The higher ones ask the person to prove who they are again at the point of doing them, and record that they did.

You do not configure this per screen. It is a property of the action, the same at every school, and it is what makes it safe for a child’s secret to be reversible at all.

What a school cannot do

A school’s administrators cannot weaken the protection on another school’s data, and cannot reach a login as a login – only the role that login holds at your school. This matters most for a member of staff shared between two schools: neither school’s administrators can act on the person, only on their place in that school.

The handful of things that reach across schools are ours, and they are on our side of the product for that reason.