# ISC documentation "Gets connector list" shows non-existing scope

**URL:** <https://developer.sailpoint.com/discuss/t/isc-documentation-gets-connector-list-shows-non-existing-scope/91554>\
**Category:** Bugs\
**Created:** [December 2, 2024, 2:49pm UTC](https://developer.sailpoint.com/discuss/t/isc-documentation-gets-connector-list-shows-non-existing-scope/91554 "2024-12-02T14:49:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sauvee](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sauvee/32/23601_2.png) [@sauvee](https://developer.sailpoint.com/discuss/u/sauvee)\
**Post date:** [December 2, 2024, 2:49pm UTC](https://developer.sailpoint.com/discuss/t/isc-documentation-gets-connector-list-shows-non-existing-scope/91554/1 "2024-12-02T14:49:18Z")

</div>

# What problem are you observing?

The documentation for the “Gets connector list” lists a required scope that does not exist.

> **[get-connector-list | SailPoint Developer Community](https://developer.sailpoint.com/docs/api/v2024/get-connector-list)**
>
> The SailPoint Developer Community has everything you need to build, extend, and automate scalable identity solutions.

Authorization: oauth2  
type: Personal Access Token  
scopes: **idn:connector-source-config:read**  
user levels: ORG\_ADMIN

# What is the correct behavior?

It should list a scope that does exist within ISC.

# What product feature is this related to?

This applies to ISC.

# What are the steps to reproduce the issue?

Please review the documentation.

# Do you have any other information about your environment that may help?

N/A

---

<div class="post-metadata">

**Author:** ![adamian](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@adamian](https://developer.sailpoint.com/discuss/u/adamian)\
**Post date:** [December 4, 2024, 7:55am UTC](https://developer.sailpoint.com/discuss/t/isc-documentation-gets-connector-list-shows-non-existing-scope/91554/2 "2024-12-04T07:55:34Z")

</div>

I’ve reported a similar issue in September (which is still not fixed), and it seems SailPoint doesn’t want to check that all document scopes can be selected in the UI. We have to create for each missing scope a ticket and wait a couple of months.

> [@Remove Account API + API Token Scope](https://developer.sailpoint.com/discuss/t/remove-account-api-api-token-scope/81799/3):
>
> Thanks for creating the ticket, Colin. Will this ticket cover all missing scopes, or do we have to create a bug report for each missing scope?

I thought solving a class of problems at once would be more efficient than solving the same problem over and over again, with all the overhead of detecting the issue, reporting it, creating an internal ticket, discussing about the priority, planning it over months, working on the issue, testing the issue, deploying the issue, ~~informing the customers that the issue is resolved~~ , the customer testing the issue themselves.  
Well… I guess we won’t be informed when the issue is resolved.