What is a School Tech Lead
A School Tech Lead is a staff user role in Clever with additional permissions. District Admins can assign certain users the School Tech Lead role which provides them with a set of specific permissions in Clever for their associated school(s).
For instructions on how a district admin can assign a staff member to the School Tech Lead Role, please see: Clever Roles: School Tech Lead
These permissions are designed to empower this user in their role as an edtech coach, instructional technology specialist, digital learning specialist, etc. Users with School Tech Lead permissions are often the individual at a school who evaluate, rollout, support, and troubleshoot technology.
School Tech Leads play an important role in helping teachers and students access your application through Clever. Learn more about their permissions and how you can collaborate with them to drive engagement for your application.
School Tech Lead tools and permissions
In the past, School Tech Leads only had limited admin permissions. In July 2020, Clever launched a new and improved user experience to empower School Tech Leads. They have the following tools in Clever:
Help districts roll out edtech
Help train teachers and students
- Demoing teacher and student accounts
- Become a certified Clever Trainer
- Access all new Clever Academy training for School Tech Leads
Quickly resolve issues with new troubleshooting tools
- Temporarily access a teacher’s portal
- Troubleshoot logins to quickly diagnose the root cause of access issues
Recommend vetted edtech apps in Clever Library
How School Tech Leads interact with your apps
School Tech Leads (STL) play an important role in helping teachers and students access your application through Clever. There are three ways a School Tech Lead might interact with your application:
- SSO into your application: If you have shared data with the staff user role for School Tech Leads.
- Viewing your application in the school’s portal: When customizing the school’s portal, a STL can view any applications the district has shared with that school.
- Viewing your application in the demo account: When accessing the teacher or student demo, STLs can view any applications the district shared with the demo school, Demoville Elementary.
Demo accounts for School Tech Leads
Demo accounts are designed for School Tech Leads (STLs) to view the Clever Portal as both a teacher or a student. They are often used as a tool to get familiar with the teacher and student experience in Clever, where STLs can build “model portals” for training purposes.
The demo user accounts will only see applications in their Clever Portal that have been rostered by the district and will have view access only. In the Clever Portal, it is clearly indicated to the demo user that they cannot SSO into the application.
Under the hood, a demo school called Demoville Elementary has been auto-generated within each district that’s on Clever. This demo school will appear for application partners in their Clever dashboard if a district is sharing Demoville Elementary.
Note: No action is required to provision accounts for this school. Your application will never be billed by Clever for Demoville Elementary and its demo inhabitants.
Right now, application partners do not have the ability to allow demo users from Demoville Elementary to SSO into their application. Soon, application partners will have the ability to opt-in to enabling access to your app through demo accounts on a district-by-district basis.
If you would like to disable Demoville Elementary, please contact Clever Support.