- Team features live on School and District plans with a shared roster.
- Invite people by role: teacher, counselor, or administrator.
- Role-based access controls who sees which students and which settings.
- Start with a small core team, then add staff as the workflow settles.
- Decide who owns the roster before everyone starts adding students.
Evident is stronger when the people around a student work from the same records instead of separate spreadsheets. Setting up your team well means each person can see and do exactly what their role requires, and nothing they should not.
Invite people by role
When you invite a teammate, you assign them a role rather than open everything to everyone. Invitable roles are teacher, counselor, and administrator: teachers (including paraprofessionals who log daily) work their own and shared students, counselors get support-team access, and administrators get building-wide visibility. Case managers are assigned per student on the student's page rather than invited as a separate role.
Invitations are sent from the admin area of the dashboard by an administrator who manages seats. If that is not you, ask the person who manages your building's account, and our team can point you to the right person if you are unsure.
How role-based access protects the right boundaries
Role-based access does not rank people. It makes sure each person sees the students relevant to them and cannot accidentally change settings outside their lane. A teacher shared on one student can log against that chart without being able to reassign a whole caseload.
This also keeps student data appropriately contained. Not every staff member needs to see every student in the building, and role-based access is how Evident honors that while still letting the right people collaborate.
Start with a small core team
You do not have to onboard the whole building on day one. Start with the few people who share a caseload and get the logging rhythm working among them. A small, well-coordinated core team teaches you what the rollout needs before you scale it.
Once that group is logging consistently and reports are coming out clean, adding the next set of staff is far easier, because you can hand them a working routine instead of a blank system.
Decide who owns the roster
Before everyone starts adding students, name one person who owns the roster. Without that, you end up with duplicate students and unclear ownership, which is exactly the mess a shared roster is supposed to prevent.
Roster ownership pairs well with a quick agreement on naming and which fields you fill in. A few minutes of convention up front saves a lot of cleanup later, especially if you imported students from a CSV.
Frequently asked questions
Can I invite teammates on a Pro plan?
Team invitations and the shared roster come with School and District plans. A Pro account is built for a single teacher working their own caseload.
Will every teammate see every student?
No. Role-based access controls who sees which students. A case manager sees their caseload, an administrator sees building-wide rollups, and staff log against the charts assigned to them.
Who can send invitations?
That depends on how your plan is set up. Often an administrator manages seats and invitations. If you are unsure who holds that ability, ask your admin or contact us.
How many people should I start with?
Start with the small group that shares a caseload. Get the logging routine working there first, then add more staff once the rhythm is steady.