-
Notifications
You must be signed in to change notification settings - Fork 0
Setting up a Team
Access is managed through teams rather than individual grants. A team groups the people working on a project or course, and repository permissions are assigned to the team. When someone joins or leaves, you change one team membership instead of auditing every repository.
Only organisation owners and existing team maintainers can create teams. If you need one, ask an administrator.
- Go to the organisation, open the Teams tab and choose New team.
- Name it clearly. Use the course code for a course, for example
EEE2046F, or a short project name. - Add members, and set at least one maintainer to look after it.
- Open the repository, go to Settings, then Collaborators and teams.
- Add the team and choose a permission level.
Grant the least permission that works. Most contributors need Write. Maintain suits tutors who manage issues and releases but should not change settings. Reserve Admin for the few who manage the repository itself.
For a course, create a team per course and add the cohort to it for the duration of the course. Remove them, or archive the repository, once the course ends. Never place student marks or personal data in a course repository. See the Contributing guide.