# Adding additional user\_scope param to Slack integration

**URL:** <https://community.auth0.com/t/adding-additional-user-scope-param-to-slack-integration/94577>\
**Category:** Get Help\
**Tags:** other-built-in-social-connections, connections\
**Created:** [November 16, 2022, 10:29pm UTC](https://community.auth0.com/t/adding-additional-user-scope-param-to-slack-integration/94577 "2022-11-16T22:29:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![liam-ssg](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/liam-ssg/32/26496_2.png) [@liam-ssg](https://community.auth0.com/u/liam-ssg)\
**Post date:** [November 16, 2022, 10:29pm UTC](https://community.auth0.com/t/adding-additional-user-scope-param-to-slack-integration/94577/1 "2022-11-16T22:29:02Z")

</div>

I’m trying to use auth0 to fetch some additional scopes for Slack. The documentation is here:

> **[Installing with OAuth](https://api.slack.com/authentication/oauth-v2#asking)**
>
> Using our new v2 Oauth 2.0 flow to create new Slack apps with more precise permissions.

There are two Slack connectors built into Auth0: the deprecated OAuth 2.0 connector, which doesn’t have the scopes I need (and is deprecated), and also the Sign In With Slack connector, which also doesn’t have the scopes I need. So I figured I would create a custom connector.

Authorization URL: [Something went wrong when authorizing this app. | Slack](https://slack.com/oauth/v2/authorize)  
Token URL: [https://slack.com/api/oauth.v2.access](https://slack.com/api/oauth.v2.access)  
Scopes: identity.basic,identity.email,identity.avatar,identity.team

(I actually need several additional scopes: `users:read,users:read.email,search:read`, which is why I’m not using the standard connector, but I can easily demonstrate with just the identity.\* ones.

When that custom connector is run, it passes all of those scopes in the `scope` parameter – which seems right, but according to the Slack docs, some of the scopes (all of them in my case) need to go into a `user_scope` parameter instead.

```auto
https://slack.com/oauth/v2/authorize?login_hint=&prompt=login&response_type=code&redirect_uri=xxxx&scope=identity.basic,identity.email,identity.avatar,identity.team&state=xxxx&client_id=xxxx

```

So the `scope` here should be `user_scope`, and `scope=` can probably be omitted (it definitely works when it’s blank).

I saw this post: [Pass additional scopes/permissions to a Social Connection](https://community.auth0.com/t/pass-additional-scopes-permissions-to-a-social-connection/56103)

It suggests using the management API to patch the requests. I could do that, but would that work to add an additional parameter, rather than change an existing one? Is there a different solution?

---

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [November 28, 2022, 7:58pm UTC](https://community.auth0.com/t/adding-additional-user-scope-param-to-slack-integration/94577/3 "2022-11-28T19:58:44Z")

</div>

Hi @liam-ssg,

I moved this to the #help category so you can get some help 😄.

You can pass custom params by updating the connection settings (as you’ve already mentioned).

This should work if you want to add an upstream param, if I understand you description correctly.

This doc also lays it out: [Pass Parameters to Identity Providers](https://auth0.com/docs/authenticate/identity-providers/pass-parameters-to-idps)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [December 12, 2022, 7:59pm UTC](https://community.auth0.com/t/adding-additional-user-scope-param-to-slack-integration/94577/4 "2022-12-12T19:59:20Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
