/2.0/teams/{username}/members required settings

[alexwonguhuru]

I am confused to what are the requirements to accessing this API.

Let's say I have a team called `Team-A` and I have a `Group` called `Group-A`.

`Group-A` has the following settings

I added `John` as a member to `Group-A` and added `Group-A` to have access to `Repo-A`. When `John` tries to access this API, he'll get 403 Forbidden.

If I change the team permissions of `Group-A` to allow `Create repositories`, `John` can access this API without a problem.

Is this intended?

* `John` is using Implicit OAuth with `account:read / write` enabled.

Thanks.

[Daniil Penkin · Accepted solution]

Hello @alexwonguhuru,

This endpoint is accessible by users who have more than read-only permissions to the team in question. There are two categories of such users: team admins (they can essentially make any changes to the team) and users that can create new repositories in that team (we call this category collaborators). This is independent from repository-level permissions, think of it as of account modifications scope.

So yes, when you allow someone to create repositories in a team, they become collaborators for that team and can access the endpoint in question.

I agree it's not very straightforward though, and there's no hint on what's wrong in the error response – this is something we can improve on.

Hope this helps.

Cheers,
Daniil

[alexwonguhuru]

Thank you Daniil!