In some circumstances, it may be necessary to prevent an existing user from logging in to ADAMI'm unable to pinpoint how to turn on "Deactivate User" permission for the district admin role. Is it only available for System Admin users?

o remove the ability for some users to be able to log into LaunchPad? We do not want to deactivate those people - the records will just reactivate again with the data coming from PowerSchool. What we want to do is change their "Login Enabled" flag from true to false.  

I’m interpreting “we” as Pearson. Or is this something the client can manage if we turn on that permission for them? Or maybe that’s something they can already do? I remember the launchpad team took that action on the first round of accounts that needed to be disabled from logging in. I’ll just need some clear guidance so I can get this wrapped up for them as soon as possible. We really thought the deactivate feature that was rolled out last month would take care of this issue for Guam. Thanks!

GDOE sent over a spreadsheet of users that still have access to launchpad/adam that should not. When we got that spreadsheet from them and spoke to you about it in January, I understood that we would soon have a feature available to take care of removing access for those accounts. I just need to know what steps we need to take to finally get this list of users blocked from accessing launchpad/adam.

Users at GDOE who you would like to handle this will need permission to edit Users, specifically users with the District Admin or STC role.  See screenshot below for what that permission configuration would look like. I have already made the change so that District Admins have this permission.

For users who should not have access to log in, find and open user from the User search page. Then, from the Actions menu, click on the Edit User Info option. 

The outcome of this will be that these users will NOT have the ability to log in.