<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Qlik Cloud Error: 401 Authorization Required after removal of deprecated Developer role and Enable API keys toggle in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-Error-401-Authorization-Required-after-removal-of/ta-p/2534952</link>
    <description>&lt;P&gt;&lt;FONT size="2" color="#999999"&gt;Updated 4th of February, 2026: the role and keys toggle has been removed as announced.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;The following two items were deprecated in June 2025 and removed in February 2026:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Developer role&lt;/LI&gt;
&lt;LI&gt;Enable API keys toggle&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This can lead to &lt;FONT face="courier new,courier"&gt;Error: 401 Authorization Required&lt;/FONT&gt; when executing third party API calls.&lt;/P&gt;
&lt;H3&gt;&lt;BR /&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;What actions do I need to take?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;To replace the deprecated built-in role, migrate your users away from the Developer role to a Custom Role with the required permissions (&lt;STRONG&gt;Manage API Keys&lt;/STRONG&gt;).&lt;/P&gt;
&lt;P&gt;To create and assign a replacement custom role:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;In the Administration activity center, go to &lt;STRONG&gt;Manage users&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;On the &lt;STRONG&gt;Permissions&lt;/STRONG&gt; tab, select &lt;STRONG&gt;Create new&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Name the new custom role using your organization's naming convention.&lt;BR /&gt;For example: "AllowManageAPIKeys"&lt;/LI&gt;
&lt;LI&gt;Expand&amp;nbsp;&lt;STRONG&gt;Features and Actions&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Then expand&amp;nbsp;&lt;STRONG&gt;Developer&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Set &lt;STRONG&gt;Manage API&lt;/STRONG&gt; &lt;STRONG&gt;keys&lt;/STRONG&gt; to &lt;STRONG&gt;Allowed &lt;/STRONG&gt;and press&lt;STRONG&gt; 'confirm'&lt;/STRONG&gt; to&amp;nbsp; complete the creation of the new custom role&lt;/LI&gt;
&lt;LI&gt;In the same screen, click the dropdown menu on the right side of the screen.&lt;/LI&gt;
&lt;LI&gt;Use the &lt;STRONG&gt;Assign &lt;/STRONG&gt;button&amp;nbsp;feature to find and assign the new custom role to specific users or groups. Do so specifically for those who previously had the now deprecated Developer role&lt;/LI&gt;
&lt;LI&gt;Remove the deprecated role from those users or groups&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;For additional reading on the &lt;STRONG&gt;Managed API Keys&lt;/STRONG&gt; (set to &lt;STRONG&gt;Not allowed&lt;/STRONG&gt; by default), see &lt;A href="https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Admin/permissions-scopes-capacity-model.htm#:~:text=settings%20%E2%80%94%20Content%20types-,Permission%20settings%20%E2%80%94%20Features%20and%20actions,-The%20Features%20and" target="_blank" rel="noopener"&gt;Permissions in User Default and custom roles | Permission settings — Features and actions&lt;/A&gt;.&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;When were the deprecated items removed?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;The &lt;STRONG&gt;Developer role&lt;/STRONG&gt; and&lt;STRONG&gt; Enable API keys toggle&lt;/STRONG&gt; were removed in February 2026.&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;What will happen if we fail to migrate?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;Once the Developer role has been removed, users who have not been updated to use the “&lt;STRONG&gt;Manage API keys&lt;/STRONG&gt;” = &lt;STRONG&gt;Allow permission&lt;/STRONG&gt; will:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Be unable to access the API keys UI in Profile &amp;gt; Settings&lt;/LI&gt;
&lt;LI&gt;Find their API keys &lt;STRONG&gt;disabled&lt;/STRONG&gt;, resulting in 3rd-party integrations failing (&lt;FONT face="courier new,courier"&gt;Error: 401 Authorization Required&lt;/FONT&gt;)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;API keys are &lt;STRONG&gt;not&lt;/STRONG&gt; deleted from Qlik Cloud and will automatically be re-enabled once a user has been assigned the required Manage API Keys permissions.&lt;/P&gt;
&lt;P&gt;To resolve this, a Tenant Administrator needs to act as outlined in &lt;EM&gt;What action do I need to take?&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;How was the deprecation communicated and what products were affected by the removal of the role and toggle?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;The deprecation notice was communicated in an &lt;STRONG&gt;Administration announcement&lt;/STRONG&gt; and documented on our &lt;STRONG&gt;What's New in Qlik Cloud&lt;/STRONG&gt; feed. See &lt;A href="https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Introduction/saas-change-log.htm#:~:text=Developer%20role%20and%20API%20key%20toggle%20deprecated" target="_blank" rel="noopener"&gt;Developer role and API key toggle deprecated | 6/16/2025&lt;/A&gt; for details.&lt;/P&gt;
&lt;P&gt;The following products were affacted:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Qlik Cloud Analytics&lt;/LI&gt;
&lt;LI&gt;Qlik Talend Cloud&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Related Information&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H3&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;&lt;A href="https://qlik.dev/changelog/146-developer-role-deprecation/" target="_blank" rel="noopener"&gt;Developer role and Enable API keys toggle deprecated | Qlik Developer Portal&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-An-error-occurred-when-generating-the-API-Key/ta-p/2534515" target="_blank" rel="noopener"&gt;Qlik Cloud: An error occurred when generating the ... - Qlik Community - 2534515&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Thu, 05 Feb 2026 07:12:35 GMT</pubDate>
    <dc:creator>Sonja_Bauernfeind</dc:creator>
    <dc:date>2026-02-05T07:12:35Z</dc:date>
    <item>
      <title>Qlik Cloud Error: 401 Authorization Required after removal of deprecated Developer role and Enable API keys toggle</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-Error-401-Authorization-Required-after-removal-of/ta-p/2534952</link>
      <description>&lt;P&gt;&lt;FONT size="2" color="#999999"&gt;Updated 4th of February, 2026: the role and keys toggle has been removed as announced.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;The following two items were deprecated in June 2025 and removed in February 2026:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Developer role&lt;/LI&gt;
&lt;LI&gt;Enable API keys toggle&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This can lead to &lt;FONT face="courier new,courier"&gt;Error: 401 Authorization Required&lt;/FONT&gt; when executing third party API calls.&lt;/P&gt;
&lt;H3&gt;&lt;BR /&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;What actions do I need to take?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;To replace the deprecated built-in role, migrate your users away from the Developer role to a Custom Role with the required permissions (&lt;STRONG&gt;Manage API Keys&lt;/STRONG&gt;).&lt;/P&gt;
&lt;P&gt;To create and assign a replacement custom role:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;In the Administration activity center, go to &lt;STRONG&gt;Manage users&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;On the &lt;STRONG&gt;Permissions&lt;/STRONG&gt; tab, select &lt;STRONG&gt;Create new&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Name the new custom role using your organization's naming convention.&lt;BR /&gt;For example: "AllowManageAPIKeys"&lt;/LI&gt;
&lt;LI&gt;Expand&amp;nbsp;&lt;STRONG&gt;Features and Actions&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Then expand&amp;nbsp;&lt;STRONG&gt;Developer&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Set &lt;STRONG&gt;Manage API&lt;/STRONG&gt; &lt;STRONG&gt;keys&lt;/STRONG&gt; to &lt;STRONG&gt;Allowed &lt;/STRONG&gt;and press&lt;STRONG&gt; 'confirm'&lt;/STRONG&gt; to&amp;nbsp; complete the creation of the new custom role&lt;/LI&gt;
&lt;LI&gt;In the same screen, click the dropdown menu on the right side of the screen.&lt;/LI&gt;
&lt;LI&gt;Use the &lt;STRONG&gt;Assign &lt;/STRONG&gt;button&amp;nbsp;feature to find and assign the new custom role to specific users or groups. Do so specifically for those who previously had the now deprecated Developer role&lt;/LI&gt;
&lt;LI&gt;Remove the deprecated role from those users or groups&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;For additional reading on the &lt;STRONG&gt;Managed API Keys&lt;/STRONG&gt; (set to &lt;STRONG&gt;Not allowed&lt;/STRONG&gt; by default), see &lt;A href="https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Admin/permissions-scopes-capacity-model.htm#:~:text=settings%20%E2%80%94%20Content%20types-,Permission%20settings%20%E2%80%94%20Features%20and%20actions,-The%20Features%20and" target="_blank" rel="noopener"&gt;Permissions in User Default and custom roles | Permission settings — Features and actions&lt;/A&gt;.&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;When were the deprecated items removed?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;The &lt;STRONG&gt;Developer role&lt;/STRONG&gt; and&lt;STRONG&gt; Enable API keys toggle&lt;/STRONG&gt; were removed in February 2026.&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;What will happen if we fail to migrate?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;Once the Developer role has been removed, users who have not been updated to use the “&lt;STRONG&gt;Manage API keys&lt;/STRONG&gt;” = &lt;STRONG&gt;Allow permission&lt;/STRONG&gt; will:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Be unable to access the API keys UI in Profile &amp;gt; Settings&lt;/LI&gt;
&lt;LI&gt;Find their API keys &lt;STRONG&gt;disabled&lt;/STRONG&gt;, resulting in 3rd-party integrations failing (&lt;FONT face="courier new,courier"&gt;Error: 401 Authorization Required&lt;/FONT&gt;)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;API keys are &lt;STRONG&gt;not&lt;/STRONG&gt; deleted from Qlik Cloud and will automatically be re-enabled once a user has been assigned the required Manage API Keys permissions.&lt;/P&gt;
&lt;P&gt;To resolve this, a Tenant Administrator needs to act as outlined in &lt;EM&gt;What action do I need to take?&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;How was the deprecation communicated and what products were affected by the removal of the role and toggle?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;The deprecation notice was communicated in an &lt;STRONG&gt;Administration announcement&lt;/STRONG&gt; and documented on our &lt;STRONG&gt;What's New in Qlik Cloud&lt;/STRONG&gt; feed. See &lt;A href="https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Introduction/saas-change-log.htm#:~:text=Developer%20role%20and%20API%20key%20toggle%20deprecated" target="_blank" rel="noopener"&gt;Developer role and API key toggle deprecated | 6/16/2025&lt;/A&gt; for details.&lt;/P&gt;
&lt;P&gt;The following products were affacted:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Qlik Cloud Analytics&lt;/LI&gt;
&lt;LI&gt;Qlik Talend Cloud&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Related Information&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H3&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;&lt;A href="https://qlik.dev/changelog/146-developer-role-deprecation/" target="_blank" rel="noopener"&gt;Developer role and Enable API keys toggle deprecated | Qlik Developer Portal&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-An-error-occurred-when-generating-the-API-Key/ta-p/2534515" target="_blank" rel="noopener"&gt;Qlik Cloud: An error occurred when generating the ... - Qlik Community - 2534515&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Thu, 05 Feb 2026 07:12:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-Error-401-Authorization-Required-after-removal-of/ta-p/2534952</guid>
      <dc:creator>Sonja_Bauernfeind</dc:creator>
      <dc:date>2026-02-05T07:12:35Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Cloud: Removing the deprecated Developer role and Enable API keys toggle (November 2025)</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-Error-401-Authorization-Required-after-removal-of/tac-p/2536545#M16570</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;We assigned new custom role to the users who are previously in the "Developer" role&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sanrout_0-1763537848871.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/185109i8679C877C5364452/image-size/medium?v=v2&amp;amp;px=400" role="button" title="sanrout_0-1763537848871.png" alt="sanrout_0-1763537848871.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Shankar&lt;/P&gt;</description>
      <pubDate>Wed, 19 Nov 2025 07:39:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-Error-401-Authorization-Required-after-removal-of/tac-p/2536545#M16570</guid>
      <dc:creator>sanrout</dc:creator>
      <dc:date>2025-11-19T07:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Cloud: Removing the deprecated Developer role and Enable API keys toggle (November 2025)</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-Error-401-Authorization-Required-after-removal-of/tac-p/2542292#M16822</link>
      <description>&lt;P&gt;Really poor to way of implementing this change. This is a breaking change. Qlik should have created a new custom role by default if the tenant had API keys issued.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2026 15:22:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-Error-401-Authorization-Required-after-removal-of/tac-p/2542292#M16822</guid>
      <dc:creator>GreenLantern</dc:creator>
      <dc:date>2026-02-03T15:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Cloud Error: 401 Authorization Required after removal of deprecated Developer role and Enable API keys toggle</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-Error-401-Authorization-Required-after-removal-of/tac-p/2542433#M16826</link>
      <description>&lt;P&gt;We are waiting for the RCA of this change.&lt;/P&gt;&lt;P&gt;We had multiple SaaS customers affected by this.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 14:25:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-Error-401-Authorization-Required-after-removal-of/tac-p/2542433#M16826</guid>
      <dc:creator>SivenM2020</dc:creator>
      <dc:date>2026-02-05T14:25:20Z</dc:date>
    </item>
  </channel>
</rss>

