The "API Key Authorization Configuration" button is disabled.

[kimutaehoon0831]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Hello,

I’m currently using an Enterprise Plan at my company, and our Dify account is accessed via a custom domain (https://dify-3.dashflow.work/) rather than the standard Dify domain.

The issue I’m facing is that the API Key Authorization Configuration button is disabled on my account. I suspect this may be because, immediately after creating my account, I imported a workflow (as a YAML file) from my previous account. During this process, tools linked to the workflow were automatically installed, which may have caused the API Key Authorization option to become unavailable.

Since then, I have been unable to connect any API keys, regardless of which tools I install on my account.

I’ve attached relevant screenshots for your reference.
Could you please look into this issue and advise on how I can resolve it?

Thank you.

2. Additional context or comments

No response

[dosubot[bot]]

Hi @kimutaehoon0831! I'm Dosu and I’m helping the dify team.

The "API Key Authorization Configuration" button is disabled if either (1) your user role is not workspace manager/admin/owner, or (2) the tool provider you are trying to configure does not support API Key credentials in its schema. Importing a workflow or using a custom domain does not dynamically disable this option—those actions only ensure required providers are present. If the imported provider doesn't support API keys, the button will be disabled by design, not as a side effect of the import process.

To resolve this, first check that your account has the necessary workspace permissions (admin/owner/editor). Next, verify that the tool provider supports API Key credentials—this is a static property defined in the provider's schema and can't be changed by importing workflows or installing tools. If you have the right permissions and the provider supports API keys but the button is still disabled, try clearing your browser cache, logging out and back in, or restarting Dify services to resolve any frontend/backend sync issues.

If you need to enable API Key support for a provider, an admin or developer must update the provider's definition to include API Key credential support. This is not something that can be changed from the UI or by importing workflows.
Relevant code references:

• Frontend logic for button state
• Backend permission and provider schema checks

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[kimutaehoon0831]

Dear Dosu,
Thank you for your prompt response!
I currently have editor permissions on my account, so I believe I should be able to connect API keys.

Regarding your suggestion to “verify that the tool provider supports API Key credentials,” I can confirm that all of the tools I’m trying to connect do support API key integration.

I have also tried clearing my browser cache and attempted to access the page from a different PC, but the issue persists.

Notably, this problem only occurs on my account—all of my colleagues have the API Key Authorization button enabled and are able to connect API keys without any issues.

[dosubot[bot]]

Based on the backend code and recent support threads, only users with admin or owner roles can configure API keys—even if the UI or documentation suggests editor is sufficient. Editors are not permitted to add or update API tool provider credentials, which is why the button is disabled for your account, but enabled for your colleagues if they have admin or owner roles. I recommend asking your workspace admin to temporarily escalate your role to admin, then refresh your session and check if the button becomes enabled. If it works, you can revert your role afterward. This is a role-based restriction, not an account-specific bug or a result of workflow import.
Reference: backend role checks

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}