<?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>idea Access Level for API Keys (data privacy) in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/Access-Level-for-API-Keys-data-privacy/idi-p/1811382</link>
    <description>&lt;P&gt;Currently a user with the Developer Role and an API Key can access all data available via API including user information and there is no option to limit the access to defined functions or non user data.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This leads to issues with granting the Role and access to APIs due to worker council / data privacy topics as the user could access this data so only selected people could get access.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There are many use cases a user would need a API Key (Qlik Data Transfer, Automation via API) without the need of accessing user data (like the Audit API user Events) and for many customers could not get this assigned due to the mentioned regulations on data security / worker council.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Beside an option of what API also a anonymized option would be useful where no user id / names are available.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 12 Dec 2022 21:34:47 GMT</pubDate>
    <dc:creator>DanielZandersQlik</dc:creator>
    <dc:date>2022-12-12T21:34:47Z</dc:date>
    <item>
      <title>Re: Access Level for API Keys (data privacy) - Status changed to: Open - Collecting Feedback</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Access-Level-for-API-Keys-data-privacy/idc-p/1814986#M6492</link>
      <description />
      <pubDate>Mon, 14 Jun 2021 17:42:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Access-Level-for-API-Keys-data-privacy/idc-p/1814986#M6492</guid>
      <dc:creator>Jeffrey_Goldberg</dc:creator>
      <dc:date>2021-06-14T17:42:30Z</dc:date>
    </item>
    <item>
      <title>From now on, please track this idea from the Ideation por...</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Access-Level-for-API-Keys-data-privacy/idc-p/2105664#M15002</link>
      <description>&lt;P&gt;From now on, please track this idea from the Ideation portal.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;A title="Link to new idea" href="https://ideation.qlik.com/app/#/case/274731" target="_blank" rel="noopener"&gt;Link to new idea&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Meghann&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;EM&gt;NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you &lt;STRONG&gt;only&lt;/STRONG&gt; see 1 tab with the login page, please try clicking this link first: &lt;STRONG&gt;&lt;A title="Authenticate me!" href="#" target="_blank" rel="noopener"&gt;Authenticate me!&lt;/A&gt;&lt;/STRONG&gt;&amp;nbsp;t&lt;/EM&gt;&lt;EM&gt;hen try the link above again. Ensure pop-up blocker is off.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Aug 2023 17:14:46 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Access-Level-for-API-Keys-data-privacy/idc-p/2105664#M15002</guid>
      <dc:creator>Meghann_MacDonald</dc:creator>
      <dc:date>2023-08-14T17:14:46Z</dc:date>
    </item>
    <item>
      <title>Re: Access Level for API Keys (data privacy) - Status changed to: Closed - Archived</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Access-Level-for-API-Keys-data-privacy/idc-p/2105665#M15003</link>
      <description />
      <pubDate>Mon, 14 Aug 2023 17:14:47 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Access-Level-for-API-Keys-data-privacy/idc-p/2105665#M15003</guid>
      <dc:creator>Ideation</dc:creator>
      <dc:date>2023-08-14T17:14:47Z</dc:date>
    </item>
  </channel>
</rss>

