https://linen.dev logo
slack scopes misconfiguration
# 🖥│support-forum
s
@Uday I tried creating a Slack auth config with minimal scopes: channels:read, users:read, users:read.email, chat:write, im:write but after creation, all default scopes get auto-added (like calls:read, files:write, etc.). Also, when editing scopes — adding or removing — the changes don’t persist after refreshing, so it seems like a bug. One more question: can we customize the connection link / consent flow (e.g. https://connect.composio.dev/...) with our own branding or domain? As a platform (Infina), asking users to trust a third-party domain during OAuth makes it harder to build confidence around data privacy.
u
Hey @sudhir_sars, it seems like a bug on our end. Let me check with the team and revert back. Also, yes, you can White label your auth flow: https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen
s
But to use this approach of auth branding, we need to use our own credentials, which in turn triggers app verification — a whole hassle to deal with, especially for restricted scopes from Google.
u
Yes, you need use your own credentials if you want to customize your auth consent screen. Also, if you are looking to customize the connection initiation screen via
link
[method](https://docs.composio.dev/changelog/2025/9/15), you can find it in [settings](https://platform.composio.dev/?next_page=settings/auth-screen) under Auth screen tab. https://cdn.discordapp.com/attachments/1431176329696383026/1431188421316972594/Screenshot_2025-10-24_at_13.21.14.png?ex=68fc8195&is=68fb3015&hm=b703e138bf91e23cb8f14aff418bedb70fdb0fc072dbe504d0865d26d3097043&
s
Hello... I have the same need here to customize consent screen. I was able to use link() and got the first screen worked with my app logo + name based on "Project Setting". However, after I hit "Contniue", it opened the 2nd screen asking to select Notion Pages. How do I white-label this screen then? If not, can I avoid to show it? P.S. I am trying to connect Notion. Thanks! https://cdn.discordapp.com/attachments/1431176329696383026/1432118776328884224/image.png?ex=68ffe40b&is=68fe928b&hm=bf3d015d7bf08f45907ba2203798ba77dce9c1e60d78656a79f8de3dd0fe7eee&
a
You need to use custom creds. Learn more here: https://docs.composio.dev/docs/custom-auth-configs
s
Thanks. Is that possible your white-label solution also can cover 2nd page as well? If you can do it for the first page, why not 2nd one?
a
The 2nd page ie the OAuth consent screen is is out of our control because it uses the configuration from the OAuth app (the logo & company name).
s
Thanks, @abhishekpatil4 But, i just referring to the brand name "Composio" there. I understand permission menu is controlled by Notion side. All i want to is to ensure our brand is shown to our users on Notion Integration. See here, another place that is showing Composio brand name, not our app name. https://cdn.discordapp.com/attachments/1431176329696383026/1436882007870275736/image.png?ex=69113826&is=690fe6a6&hm=c61a2e5a135e097d5b7077a8fa0ffc48e5f32a2fe0d2b60280bac15e21b6b0f3&
a
Got it, Notion APIs use the OAuth app’s name and logo, you need to change this by using your own OAuth app to have your company’s name shown instead.
s
I see. Basically, Composio is the registered OAuth app at Notion side. We leverage Compsio to mange OAuth workflows and tool integration workflows via AI. If I am going to plan B which is to register our App as OAuth App, is there any way to still integrate Compsio to get other benefits? Or register your OAuth App will go down a whole new integration plan, then, we can't work with Compsio. We will have to build rest like traditional app integration or using n8n/zapier workflow orchestration, maybe? Thanks for helping my request. 🙂
a
you can do that with composio - check
s
Okay. Will give a try. Thanks!
d
digging up an old thread mb! looks like all of these docs are not working anymore, all redirecting to the same page cc: @abhishekpatil4 also, i know you could turn off the Auth Screen Configuration— where in the settings could we do that without needing to add our own configs? like tavus?
a
Hey, the docs was a temporary issue and is fixed now. > turn off the Auth Screen Configuration If I understand correctly you want to bypass the Auth Screen page?
d
yes, if that’s possible
a
Yes, you can use the
.initiate()
method:
this doesn't exist
i'm on installed @composio/core@0.2.4 12 packages installed [1208.00ms]
@Uday
Are you using the client by any chance? (
composio.getClient()
)
d
oh yes, it was because it's @composio/client