Google Workspace for Education - Adding Teacher to Classroom

[simpsonj]

Thanks both, works well.

 

One quick question, using that command makes the 'new' teacher the owner, is there a way to must make them a teacher? It's not the end of the world, just means my cover supervisors are going to be owners of a lot of classes, and owners are harder to get rid of!

[simpsonj]

That link you shared @F_admin is very useful!

 

Or I could use the right syntax when adding a teacher!

Edited March 18, 2022 by simpsonj
Mistake!

[RLR]

Thanks both, works well.

 

One quick question, using that command makes the 'new' teacher the owner, is there a way to must make them a teacher? It's not the end of the world, just means my cover supervisors are going to be owners of a lot of classes, and owners are harder to get rid of!

 

I don't believe this is how it works as there is a separate command to making a teacher an owner:

gam update course owner

 

Plus, to make a teacher an owner, they need to be part of the class already:

https://sites.google.com/jis.edu.bn/gam-commands/services/classroom#h.p_ZzCeeHvUNR8o

[RLR]

Might be worth noting that there is a limit of 20 teachers allowed in a classroom.

[jthompson]

This might be another useful one to bookmark - https://gamcheatsheet.com/GAM%20Cheat%20Sheet%20A3.pdf

 

In terms of finding out the required course ID, if you have the security investigation tool in Google Admin (requires one of the paid-for tiers, iirc) then you can leverage that to get at a course id as well. Generally, though, I tend to do what @RLR has suggested with the gam command.

 

If you're using gam in Google Cloud Shell, then

 

gam print courses teacher [email][email protected][/email] > classesTheTeacher.csv

followed by

 

cat classesTheTeacher.csv

to view the output.

 

It's pretty ugly to read like that, so downloading the csv file from Cloud Shell (three pips -> download -> type name of file) and opening it in a spreadsheet app should make it easier to pick out the right id to use. Probably worth also deleting the csv from Cloud Shell as well, to avoid crap building up over time.

 

rm classesTheTeacher.csv

[Planehazza]

sorry for the thread necro, but I've just come back to GAM after playing with it a good year ago. Am I right in saying you need a project per instance? Or can multiple GAM instances rely on the same project?

 

Cheers!

[jthompson]

sorry for the thread necro, but I've just come back to GAM after playing with it a good year ago. Am I right in saying you need a project per instance? Or can multiple GAM instances rely on the same project?

 

Cheers!

 

Multiple instances can use the same project. You just need to reuse the Oauth files from the project, dropping them into place for each instance.

• client_secrets.json
  
• oauth2.txt
  
• oauth2service.json
  

 

Those files basically represent the keys to the kingdom (whoever has them has your Google Workspace domain!), so store them in a password manager or somewhere equally secure. I'd also strongly recommend only installing GAM to Google Cloud Shell, and running it from there. That would prevent you having to have those super-sensitive files held locally on Windows machines. It also means that you can access GAM via your Google login from any web browser.