- Single sign-on lets staff use their existing district login.
- Provisioning automates creating and removing accounts as staff change.
- Both are typically arranged at the School or District plan level.
- Your district technology team is the right partner for setup.
- For specifics on supported methods, contact us; we describe it generically here.
For larger deployments, schools usually want staff to sign in with their existing district credentials and to have accounts created and removed automatically. Here is how that generally works with Evident and who to bring into the conversation.
What single sign-on does for staff
Single sign-on, often shortened to SSO, lets staff sign in to Evident with the same credentials they already use across district systems, rather than maintaining a separate password. For a building, that means one fewer login to manage and one fewer way for access to go stale.
The practical benefit is adoption. When signing in is the same motion staff already know, you remove a small but real barrier to using the tool every day.
What provisioning handles
Account provisioning is about lifecycle: creating accounts when staff arrive and removing access when they leave or change roles, ideally without an administrator doing it by hand for each person. At district scale, automating this keeps the staff list accurate and closes a common security gap, the account that lingers after someone departs.
Provisioning and role-based access work together. Provisioning decides whether an account exists; role-based access decides what that account can see once it does.
Where this fits in your plan
These capabilities are arranged at the School or District level, where there is a shared roster and an administrator coordinating access for many staff. On an individual Pro account there is nothing to provision, since it is one teacher signing in for themselves.
If you are evaluating Evident for a building or district and SSO or provisioning is a requirement, raise it early. It is a setup conversation, not a checkbox, and it is easier handled during onboarding than retrofitted later.
Who to involve
The right partner on your side is your district technology team. They own the identity systems staff already sign in with, and they will know what your district supports and requires for a new tool.
On our side, bring us into that conversation early. Rather than assert a specific method here that may not match what your district uses, we will walk through the options that fit your environment together.
Frequently asked questions
Which sign-on systems does Evident support?
We describe this generically rather than naming methods that may not match your environment. For a precise answer for your district, contact us and we will go through the supported options with your technology team.
Do I need SSO to use Evident?
No. Single sign-on is a convenience and security feature for larger deployments. Individual teachers and small teams sign in directly without it.
What does provisioning actually save us?
It keeps your account list accurate by creating and removing access as staff change, without an administrator doing it by hand. That closes the common gap of an account lingering after someone leaves.
Who should set this up?
Your district technology team, with us. They own the identity systems; we walk through the options that fit your environment. Raise it early during onboarding rather than later.