kind:change

title:Breaking changes to organization permissions are now official

created_at:2015-06-24

author_name:jakeboxer

As[promised earlier this month][notice], the[API changes][api-changes] related to managing organization members and repositories are now official parts of the GitHub API.

During the migration period, you needed to[provide a custom media type in the`Accept` header][migration-period] to opt-in to the changes. Now that the migration period has ended, you no longer need to specify this custom[media type][media-types].

If you have any questions or feedback, please[get in touch with us][contact]!

[notice]:/changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24

[api-changes]:/changes/2014-12-08-organization-permissions-api-preview/

[contact]:https://github.com/contact?form[subject]=Organization+Permissions+API

[media-types]:/v3/media

[migration-period]:/changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24/#migration-period

Next, we want to opt in to the[upcoming improvements to the repository listing API][list-repositories-for-current-user]. To do so, we'll set the media type that gives us access to that functionality.

Now, we'll pass in our application's[OAuth token for a given user][make-authenticated-request-for-user]:

Next, we'll pass in our application's[OAuth token for a given user][make-authenticated-request-for-user]:

Next, we'll opt in to the[upcoming enhancements to the organization listing API][list-orgs-for-current-user]. To do so, we'll set the media type that gives us access to that functionality.

Now, we'll pass in our application's[OAuth token for a given user][make-authenticated-request-for-user] to initialize our API client:

Next, we'll pass in our application's[OAuth token for a given user][make-authenticated-request-for-user] to initialize our API client:

Currently,[OAuth](/v3/oauth/#scopes) requests always receive the user's[public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership), regardless of the OAuth scopes associated with the request. If the OAuth authorization has`user` or`read:org` scope, the response also includes private organization memberships.

With the new Organization Permissions API (described below), this method will only return organizations that your authorization allows you to operate on in some way (e.g., you can list teams with`read:org` scope, you can publicize your organization membership with`user` scope, etc.). Therefore, this API will require at least`user` or`read:org` scope. OAuth requests with insufficient scope will receive a`403 Forbidden` response.

<divclass="alert">

<p>

</p>

<p>

</p>

</div>

This only lists organizations that your authorization allows you to operate on in some way (e.g., you can list teams with`read:org` scope, you can publicize your organization membership with`user` scope, etc.). Therefore, this API requires at least`user` or`read:org` scope. OAuth requests with insufficient scope receive a`403 Forbidden` response.

List[public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.

Currently, if you make an authenticated call, you can also list your private memberships in organizations (but only for the currently authenticated user).

With the new Organization Permissions API (described below), this method will only list*public* memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the[List your organizations](#list-your-organizations) API instead.

<divclass="alert">

<p>

</p>

<p>

</p>

</div>

This method only lists*public* memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the[List your organizations](#list-your-organizations) API instead.

Name | Type | Description

--------|---------|--------------

`filter`|`string` | Filter members returned in the list. Can be one of:<br/>*`2fa_disabled`: Members without[two-factor authentication][2fa-blog] enabled. Available for organization admins.<br/>*`all`: All members the authenticated user can see.<br/><br/>Default:`all`

`role` |`string` | Filter members returned by their role. If specified, must be set to`admin`, which will only return users with admin permissions on the org.**This parameter requires a custom media type to be specified. Please see more in the alert below.**

`role` |`string` | Filter members returned by their role. If specified, must be set to`admin`, which will only return users with admin permissions on the org.

[2fa-blog]:https://github.com/blog/1614-two-factor-authentication

<divclass="alert">

<p>

</p>

<p>

</p>

</div>

<%= headers 200,:pagination => default_pagination_rels %>

<divclass="alert">

<p>

</p>

<p>

</p>

</div>

In order to get a user's membership with an organization, the authenticated user must be an organization admin.

<divclass="alert">

<p>

</p>

<p>

</p>

</div>

In order to create or update a user's membership with an organization, the authenticated user must be an organization admin.

<divclass="alert">

<p>

</p>

<p>

</p>

</div>

In order to remove a user's membership with an organization, the authenticated user must be an organization admin.

List repositories for the authenticated user.

Note that this currently does not include repositories owned by organizations

which the user can access. You can

[list your organizations](/v3/orgs/#list-your-organizations) and

[list organization repositories](/v3/repos/#list-organization-repositories)

separately.

With the new Organization Permissions API (described below), this*will* include

repositories owned by organizations which the user can access. If you provide

the custom media type (described below), you won't need to use other APIs to

list the authenticated user's organization-owned repositories.

<divclass="alert">

<p>

</p>

<p>

</p>

</div>

List repositories that are accessible to the authenticated user.

This includes repositories owned by the authenticated user, repositories where

the authenticated user is a collaborator, and repositories that the

authenticated user has access to through an organization membership.