Skip to main content
Mattyb156
Participant
May 29, 2026
Question

Adobe for Creativity" Claude connector blocked on Teams plan — "Your organization does not allow access to third party applications"

  • May 29, 2026
  • 2 replies
  • 8 views

Hi all,

Posting here because I've hit a wall with chat support and I've seen at least one other thread describing the same issue, so I'm hoping a moderator or product team member can weigh in.

**The setup:**
- I'm the System Administrator on our Adobe Teams (Business) plan.
- I'm trying to install the official "Adobe for Creativity" connector inside Claude (the Anthropic/Adobe MCP integration launched April 28, 2026).
- When I click Connect in Claude and the Adobe sign-in window opens, it fails immediately with: **"Your organization does not allow access to third party applications."**
- The window header shows "Enterprise ID" and the URL is https://adobeid-na1.services.adobe.com/ims/fromSusi.

**What I've already verified:**
- "Allow users to integrate apps" is enabled in Admin Console > Products > App Integrations.
- Claude does not appear in the "Add App Integrations" list and there's no Claude entry under "User-accepted integrations."
- Tried multiple browsers, incognito, cleared cache, different network. Same error every time.
- The error fires before any login is possible, so I can't authenticate even as the admin.

**What chat support told me:**
I was told the granular third-party app management is only available on Enterprise (ETLA) deployments, and that to fix this I would need to upgrade from Teams to Enterprise (they gave me a sales number). The agent acknowledged they were not from the Enterprise department.

**My questions for the community / moderators:**
1. Is the Adobe for Creativity Claude connector officially supported on Teams (Business) plans? Adobe's launch messaging positions it for creators and small businesses, not just Enterprise.
2. If yes, what is the actual admin step to allow it, given it doesn't appear in the Add App Integrations list?
3. If it's genuinely Enterprise-only, can someone from Adobe confirm that publicly so Teams customers know not to expect this integration?

Has anyone else on a Teams plan gotten this connector working? Would love to hear what worked.

Thanks!

    2 replies

    Mattyb156
    Mattyb156Author
    Participant
    May 29, 2026

    Good morning - I have tried both steps and both have failed.  I am on Claude Max plan.   I am not on a teams and enterprise plan.  As for Adobe, I believe I have a teams plan that is for my Non-Profit, I am the only one in the account and am the administrator. Please help as this setup should ber allowable based on all the feedback I have read.

    Community Manager
    May 29, 2026

    Hi ​@Mattyb156,

     

    Thank you for trying those steps and coming back so quickly. We're sorry neither worked, and we understand the frustration of having done everything correctly on your side and still being stopped at the sign-in window.

     

    Based on what you've shared:

    • On the Claude side, Claude Max is an individual plan, so the 3P Connectors toggle under Organization settings does not apply to your account, and the connector should be addable directly from your personal Claude profile, which is the path you tried.
    • On the Adobe side, you are the System Administrator on a Creative Cloud for Teams (Non-Profit) plan with "Allow users to integrate apps" enabled, and you've tried multiple browsers, incognito, cache clears, and different networks.

    Both entitlements are in place and the admin-side settings you control are already in the right state, so the next step is to have our support team look at the specific restriction on your Adobe organization account.

    Please open a chat through Admin Console > Support. Starting a chat will automatically create a case. When you reach the agent, share the following:

    • You are attempting to install the Adobe for creativity MCP connector from Claude (https://developer.adobe.com/adobe-for-creativity/getting-started/)
    • The exact error: "Your organization does not allow access to third party applications"
    • The error appears at the Adobe sign-in window (URL beginning with adobeid-na1.services.adobe.com/ims/fromSusi) before you can enter credentials
    • You have already verified "Allow users to integrate apps" is enabled and tested across multiple browsers, incognito, cache clears, and different networks
    • You are on a Creative Cloud for Teams (Non-Profit) plan and you are the System Administrator

    Please let us know how it goes, we're happy to assist further.

    Thanks,

    ^BS

    Mattyb156
    Mattyb156Author
    Participant
    May 29, 2026

    I tried to do as you said and the rep adamantly said that this a claude issue - not adobe and will not set up help ticket.  Said your direction was wrong.  what is going on?

     

    Community Manager
    May 29, 2026

    Hi ​@Mattyb156,

     

    Thank you for the detailed write-up, and we're sorry you've hit this wall. We understand how frustrating it is to do all the right diagnostic steps, get conflicting guidance from chat support, and still be stuck at a sign-in window that won't let you past the first screen.

     

    To summarize where you are: as a System Administrator on a Creative Cloud for Teams plan, you're trying to install the Adobe for creativity connector from inside Claude, and the Adobe sign-in window throws "Your organization does not allow access to third-party applications" before you can authenticate. You've already confirmed the App Integrations setting is enabled, tried multiple browsers and networks, and cleared the cache.

     

    A few clarifications to set the right expectations, based on the official setup documentation and a recent thread where other admins worked through the same error (reference thread here):

    1. The Adobe for creativity connector is configured from Claude's side, not the Admin Console. It uses the MCP (Model Context Protocol) and is added via Claude's Settings > Connectors. It will not appear under Add App Integrations in the Admin Console, as that section is specifically for apps from the Adobe Exchange marketplace. Its absence from that list is expected and does not cause the error. Setup reference: https://adobe.ly/4uF9SkM

    2. The connector is not Enterprise-exclusive, but it does require setup on both sides:

    • On the Adobe side: an Adobe organization with admin setup, and users must have access to the relevant Creative Cloud products. Some advanced governance and security controls, such as SSO, advanced identity management, and enterprise governance, are available on Enterprise plans only. The connector itself works on Teams.

    • On the Claude side: the connector requires a Claude Team or Claude Enterprise plan. A Claude owner or admin must enable 3P Connectors under Organization settings > Skills before members can use the full connector experience. On Claude Pro or Claude Free, this organization-level setting does not exist, and the connector can only be added under a personal Claude profile rather than an organization workspace.

    3. Two fixes have worked for admins seeing this exact error:

    • Fully clear the browser cache and cookies, then retry the connector setup. One admin on the prior thread confirmed this resolved the error after a complete clear, not just a tab refresh.

    • Connecting from a personal Claude profile rather than a company or organization Claude profile. Another admin found that selecting their personal profile in Claude before initiating the connector allowed it to complete, and the connection then carried across their workstations. This is the path that applies if your organization is on Claude Pro rather than Claude Team or Enterprise.

     

    Please let us know which Claude plan your organization is on: Claude Pro, Claude Team, or Claude Enterprise. That will tell us whether the 3P Connectors toggle on Claude's side is the missing step, or whether the personal-profile path is the right one for your setup.

     

    Please share that detail and try the cache clear in the meantime, and we'll take it from there.

     

    Thanks,

    ^BS