@sanicki: As requested, here is a screenshot of a group assignment I attempted to create (note this is re-visiting the assignment after it has been created–hence no form blanks related to teams are present):
Logging in as a fictional student and following the assignment link, I’m presented with this screen:
(which I choose to skip)
moving to the next screen
I am given the option of joining an existing team (that I created during earlier experimentation).
My confusion stems from my creation of teams within the organisation and the assignment of members to those team organisations. I was under the impression that my creation of teams was the mechanism by which I could have control of team membership for group projects. This appears to be my misunderstanding; your initial statement (in a different issue) that team assignment is student-centric being the clue I needed.
However, continuing the example you requested, here is the next screen grab following from this student choosing to create a new team, named “My new team”
At this point, the student received this 404 message, however, the instructor (as owner of the organisation) receives this success email message:
The import to https://github.com/StAndrewsStats/p5-my-new-team is finished!
Finally, as the student, I visit the new repo, just cloned, I see this
The team repo has been created, and it is labelled as private. When I log on to Github as a different student, I get a 404 message as expected. This is what I intended to prevent members of teams from viewing contents of repos of which they are not members.
Hence, in the end, I think I have accomplished what I wanted; but for this to work I am reliant upon the students to correctly assign themselves to the teams I specified, using the team names I specify.
The other challenge presented is the 404 message students receive upon following the link to the assignment. Hopefully that won’t be too off-putting to them.