Q: Will we have the ability to control who has access to our repositories?
A: Yes. By default, a repo created in one of the organizations under the Tufts enterprise will be “internal,” which means that anyone in the org has read access. You can further limit read and write access by changing the individual repo’s settings and/or creating groups and using the groups to grant permissions.
Q: Is it possible to make a repo public?
A: Yes, go to the repo settings. See: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility
Q: Can we get our own Github organization for our group/team/department?
A: This is potentially possible, but there are caveats which mean it might not be the best solution in the end. Please see: Notes On Github Organizations
Q: Can I use my existing Github account or do I have to create a new one?
A: You can do either. Github handles SSO slightly differently than other platforms, and you’ll basically need to auth a second time to access any resources that belong to an organization. This means that you can use a pre-existing Github account (and that all of your personal repos will stay as-is) or create a new one if you’d like to keep things absolutely separate. Either way, organization members will not be able to access your personal repos unless they are already set to public visibility or you give them access via another means.