How to make users inactive

Marking users as inactive is the best way to remove access to your school for specific users - parents of alumni or teachers who no longer work at the school - without removing their data. This also allows you to reinstate the user at any time should they need access to their child's information, or if they come back to the school. 

For Staff: You can mark any staff user as "inactive" which will remove their ability to login. However, it will not disconnect that particular email address from that user, nor will it delete that person's name from any observations they entered. Any "inactive" user can be marked "active" again which restores that user's ability to login. You can mark staff "inactive" from the [Directory] > [Staff] page. Select the user and click [Mark Inactive] at the top of the page.

To view inactive staff, go to [Directory] > [Staff] and use the dropdown in the upper right to switch your view from "Active" to "Inactive". You can make a user active again by selecting them and clicking [Mark Active] at the top of the page.

For Parents: You can make any parent inactive by going to [Directory] > [Parents], checking the box next to their name, and clicking [Mark inactive]. Making a user inactive removes their ability to login to your school. If they try, they will receive the message "You do not have access to any schools". You can always mark a user active again if they need access.

Most schools allow parents access to the system for a few weeks to a month after their child leaves, to download photos or any conference reports that they want (if they have access to them), before marking the parent inactive. After marking them inactive, they would simply need to contact you if they wanted any of that information from their child's profile.

As always, please reach out to us at info@transparentclassroom.com with any additional questions, or email us directly from the website by clicking on the orange ? beacon and clicking [Ask]. 

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.