forked from docs/doc-exports
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Co-authored-by: chenxiaoxiong <chenxiaoxiong@huawei.com> Co-committed-by: chenxiaoxiong <chenxiaoxiong@huawei.com>
13 lines
1.1 KiB
HTML
13 lines
1.1 KiB
HTML
<a name="dataartsstudio_03_0158"></a><a name="dataartsstudio_03_0158"></a>
|
|
|
|
<h1 class="topictitle1">How Do I Isolate Workspaces So That Users Cannot View Unauthorized Workspaces?</h1>
|
|
<div id="body0000001893380714"><p id="dataartsstudio_03_0158__p2084791485513">In <span id="dataartsstudio_03_0158__text173031535519">DataArts Studio</span>, <strong id="dataartsstudio_03_0158__b13966559133">system roles</strong> and <strong id="dataartsstudio_03_0158__b2096617513138">workspace roles</strong> are used to assign permissions. By default, if a user is assigned the <span id="dataartsstudio_03_0158__text2630145055416">DARTS</span> User system role but not a workspace role, the user cannot view the workspace.</p>
|
|
<p id="dataartsstudio_03_0158__p19342365588">If the user is also assigned the <span id="dataartsstudio_03_0158__text1538035855410">DARTS</span> Administrator, Tenant Guest, or Tenant Administrator role, the user can view all workspaces.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dataartsstudio_03_0001.html">Consultation and Billing</a></div>
|
|
</div>
|
|
</div>
|
|
|