Good practice structure for a school

[jomynyddmerci]

Hi all,

Joanne here from Dubai. New to the role. 

Does anyone have a suggested 'best practice' structure for a school's Google environment? I need to reengineer ours so interested to know how schools have their set up.

Thanks

[NielsBrockmeier]

We have a different setup than most I have seen but still it might be interesting to see this option as well.
For us, 8 schools in 1 district, we have all our staff in one OU as a lot of staff work on multiple schools and it wasn't plausible to have the staff get the right OU in time in an automated manner. We have an automated OU structure for our classes through our scheduling software, but just the Students > School was what we had at first.

• All Staff
• Students 
  • School 1
    • Class1
    • Class2
    • Class3
    • etc.
  • School 2
    • Class1
    • Class2
    • Class3

We had, and partially still have, our directory use the department field set to their class, and we added custom schemas to add their years and school, and class there as well.

[npl]

The structure we use is

• School 
• Staff
• Students
• Year 
• Class 
• Class
• Class
• Year 
• Class 
• Class
• Class
• ............

e.g.
  Students
     /2023
      A
      B
    /2024
     A
     B

Year - is they year the class started in the school ( current new students are in class under 2024  )

We also use the year in the email ( eg current first year email 24Elizabeth.Madden@domain.com ) 

[kaned]

We followed Amplified IT's approach for OU structure which is specific to schools.

https://amplifiedlabs.zendesk.com/hc/en-us/articles/13548930860947-Building-a-K12-Org-Unit-Structure

or

https://pbs.twimg.com/media/D5gvR9PWsAEbzOq?format=jpg&name=4096x4096

[llennon]

This particular structure is scaleable and has lots of advantages on the management side. I too use it and recommend it to anyone who asks.