@@ -305,18 +305,24 @@ and get a new code.
305
305
## Directing users to review their access for an application
306
306
307
307
Users can review and revoke their application authorizations from the [ settings
308
- screen within GitHub] [ settings ] . Integrators can deep link to the authorization
309
- information for their particular app to let their end users review those
310
- details.
308
+ screen within GitHub] [ authorized-apps ] . A user's organizations [ control whether
309
+ an application can access organization data] [ org-app-policies ] . Integrators can
310
+ deep link to the authorization information for their particular app to let their
311
+ end users review these details.
311
312
312
313
To build this link, you'll need your OAuth application's ` client_id ` you
313
- received from GitHub when you [ registered the application] [ apps ] .
314
+ received from GitHub when you [ registered the application] [ owned- apps] .
314
315
315
316
https://github.com/settings/connections/applications/:client_id
316
317
318
+ For tips on discovering the resources that your application can access for a
319
+ user, be sure to check out our [ guide] [ resource-discovery-guide ] .
320
+
317
321
[ oauth changes blog ] : /changes/2013-10-04-oauth-changes-coming/
318
322
[ basics auth guide ] : /guides/basics-of-authentication/
319
323
[ deployments ] : /v3/repos/deployments
320
324
[ public keys ] : /v3/users/keys/
321
- [ settings ] : https://github.com/settings
322
- [ apps ] : https://github.com/settings/applications
325
+ [ authorized-apps ] : https://github.com/settings/applications#authorized
326
+ [ owned-apps ] : https://github.com/settings/applications
327
+ [ org-app-policies ] : /changes/2015-01-19-an-integrators-guide-to-organization-application-policies/
328
+ [ resource-discovery-guide ] : /guides/discovering-resources-for-a-user/
0 commit comments