Role synchronisation across environments - how do you do it?

[Mikee]

We have several environments (Production, Integration Testing, Development... as well as their beta shadows), and I'm really trying to avoid hopping in to each one individually to remove some people who've moved on from our team.

How do you handle account-level (admin) permissions across your environments? 

We have a high-tech onboarding checklist, but I'm hoping there's a better way to do this 🙂 

[Chris_Hofer]

Hi @Mikee ...

When I was a Canvas administrator in higher education, we had the standard "production", "beta", and "test" environments with our paid Canvas instance.  So, if there were staff changes, I'm only aware that we only made changes to our "production" environment because the "beta" and "test" environments would eventually be overwritten with data from the "production" environment.  This document describes these things in more detail:

What is the Canvas release schedule for beta, production, and test environments?

Other schools may do things differently, but I believe this is how we handled things when I was there.

Hope this helps a bit.

[Mikee]

We have 4 streams of environment - Primary, Test, and Beta across Production, DEV, SIT, and UAT - making a total of 12 quasi-separate tenancies. 

It's synchronising users across PRD, DEV, and UAT that I'm querying if anyone automated or made less prone to leaving departed staff with direct access.