Salamander - Student Accounts

[bknaggs]

I've logged this as a support request with Salamander but thought I'd ask how others who have Salamander installed do it.

 

When are your student AD accounts created? Is it when they change from Applicant to Pupil in SIMS or before then? We've got a few students starting today who are still Applicants in SIMS and our admissions team doesn't change that until they have turned up. Salamander obviously isn't seeing them yet so I'm guessing the accounts will appear overnight.

Does anyone with Salamander get their student accounts setup at an earlier stage?

[RLR]

We have salamander create accounts for our applicants. It's a separate job we run. The only downside to this job is it creates accounts for all applicants, even if they've not confirmed they're joining.

[pete]

From mid-August > mid-September, new Y7 and Y12 students are created provided the application in SIMS in a status of "accepted" or "admitted" .

Mid-year joiners are created when their application has a status of accepted or admitted. It's on the school offices to ensure that happens at least the day before the student physically arrives.

 

Realistically it's trivial for your admissions team to flag the student as "never turned up" even after the application is accepted or admitted, so it's a question of what's more of a problem - the kid being unable to login on their first day or someone in the office having to click a couple of buttons.

 

Salamander can talk you through your options.

[bknaggs]

Thanks both of you @RLR and @pete

 

I've asked Salamander to make the change to Applicant - Accepted which is what we use internally for other things. I just wanted confirmation it could be done before I started regretting getting Salamander setup.

[pete]

For the "kid didn't turn up" AD accounts, you can configure Salamander to run a cleanup routine if the student's no longer active in SIMS.

 

We have it disable the account, change description to "leaver - %datestamp%", and move to the disabled accounts OU. Note that if you're doing selective OU sync to Azure AD that OU move will disable or delete anything owned by their account in Office 365.

[RLR]

For the "kid didn't turn up" AD accounts, you can configure Salamander to run a cleanup routine if the student's no longer active in SIMS.

 

We have it disable the account, change description to "leaver - %datestamp%", and move to the disabled accounts OU. Note that if you're doing selective OU sync to Azure AD that OU move will disable or delete anything owned by their account in Office 365.

 

Thanks. Will look into this.