<?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>topic Root admin access in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Root-admin-access/m-p/1333837#M9780</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Is it possible for a root admin to restrict his own access to a stream or an app? That is, he will create a stream, he will upload an app to that stream, but then he will not be able to access that app in the Hub. How would he do that ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Is it possible for a root admin to restrict the access of another root admin to a stream or an app ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Both questions are in the context of sensitive data which must be seen only by a few people, none of them being root admin, or having knowledge about the QMC.&lt;/P&gt;&lt;P&gt;Or is there another way to approach this situation?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you !&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Apr 2017 11:02:28 GMT</pubDate>
    <dc:creator>cata_pli</dc:creator>
    <dc:date>2017-04-18T11:02:28Z</dc:date>
    <item>
      <title>Root admin access</title>
      <link>https://community.qlik.com/t5/Management-Governance/Root-admin-access/m-p/1333837#M9780</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Is it possible for a root admin to restrict his own access to a stream or an app? That is, he will create a stream, he will upload an app to that stream, but then he will not be able to access that app in the Hub. How would he do that ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Is it possible for a root admin to restrict the access of another root admin to a stream or an app ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Both questions are in the context of sensitive data which must be seen only by a few people, none of them being root admin, or having knowledge about the QMC.&lt;/P&gt;&lt;P&gt;Or is there another way to approach this situation?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you !&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Apr 2017 11:02:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Root-admin-access/m-p/1333837#M9780</guid>
      <dc:creator>cata_pli</dc:creator>
      <dc:date>2017-04-18T11:02:28Z</dc:date>
    </item>
    <item>
      <title>Re: Root admin access</title>
      <link>https://community.qlik.com/t5/Management-Governance/Root-admin-access/m-p/1333838#M9781</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1: No.&lt;/P&gt;&lt;P&gt;2: No.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In Qlik Sense 1.0 it was possible for the Root Admin to make change to the Root Admin rule and as a result lock himself out. That kinda defies the whole idea behind a root admin; "he/she with all access". We got a lot of complains of people accidentally doing this, locking themselves out of the QMC and ending up doing a shift-delete and a full reinstall. So this was fixed in QS 1.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not a legal expert, but I would make sure the root admin has signed all related privacy statements and contracts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Apr 2017 11:24:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Root-admin-access/m-p/1333838#M9781</guid>
      <dc:creator>oknotsen</dc:creator>
      <dc:date>2017-04-18T11:24:12Z</dc:date>
    </item>
  </channel>
</rss>

