Skip to content

Commit 5489bb5

Browse files
Merge pull request #250025 from normesta/gen2
Fixing a github issue
2 parents 1924937 + 57c7696 commit 5489bb5

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

articles/storage/blobs/data-lake-storage-access-control.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: normesta
66

77
ms.service: azure-data-lake-storage
88
ms.topic: conceptual
9-
ms.date: 05/09/2023
9+
ms.date: 08/30/2023
1010
ms.author: normesta
1111
ms.reviewer: jamesbak
1212
ms.devlang: python
@@ -124,6 +124,18 @@ Every file and directory has distinct permissions for these identities:
124124

125125
The identities of users and groups are Azure Active Directory (Azure AD) identities. So unless otherwise noted, a *user*, in the context of Data Lake Storage Gen2, can refer to an Azure AD user, service principal, managed identity, or security group.
126126

127+
### The super-user
128+
129+
A super-user has the most rights of all the users. A super-user:
130+
131+
- Has RWX Permissions to **all** files and folders.
132+
133+
- Can change the permissions on any file or folder.
134+
135+
- Can change the owning user or owning group of any file or folder.
136+
137+
If a container, file, or directory is created using Shared Key, an Account SAS, or a Service SAS, then the owner and owning group are set to `$superuser`.
138+
127139
### The owning user
128140

129141
The user who created the item is automatically the owning user of the item. An owning user can:

0 commit comments

Comments
 (0)