Skip to content

Commit f62e28b

Browse files
authored
Merge pull request #106871 from priestlg/gdpDBG-ManageUsers-030620
Removed erroneous/inaccurate text
2 parents 59c5514 + ed189e5 commit f62e28b

File tree

4 files changed

+10
-12
lines changed

4 files changed

+10
-12
lines changed

articles/databox-online/data-box-edge-deploy-add-shares.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ To create a share, do the following procedure:
6464

6565
f. Depending on whether you've created an SMB share or an NFS share, do one of the following steps:
6666

67-
- **SMB share**: Under **All privilege local user**, select **Create new** or **Use existing**. If you create a new local user, enter a username and password, and then confirm the password. This action assigns permissions to the local user. After you've assigned the permissions here, you can use File Explorer to modify them.
67+
- **SMB share**: Under **All privilege local user**, select **Create new** or **Use existing**. If you create a new local user, enter a username and password, and then confirm the password. This action assigns permissions to the local user. Modification of share-level permissions is currently not supported.
6868

6969
If you select the **Allow only read operations** check box for this share data, you can specify read-only users.
7070

@@ -140,7 +140,7 @@ On your Linux client connected to your Data Box Edge device, do the following pr
140140
141141
> [!NOTE]
142142
> The following caveats are applicable to this release:
143-
> - After a file is created in the share, renaming of the file isnt supported.
143+
> - After a file is created in the share, renaming of the file isn't supported.
144144
> - Deleting a file from a share does not delete the entry in the storage account.
145145
146146
## Next steps

articles/databox-online/data-box-edge-manage-users.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,7 @@ Users can be read-only or full privilege. As the names indicate, the read-only u
2828
- **Full privilege user** - A local user with full access.
2929
- **Read-only user** - A local user with read-only access. These users are associated with shares that allow read-only operations.
3030

31-
The user permissions are first defined when the user is created during share creation. After the permissions associated with a user are defined, these can be modified by using File Explorer.
32-
31+
The user permissions are first defined when the user is created during share creation. Modification of share-level permissions is currently not supported.
3332

3433
## Add a user
3534

articles/databox-online/data-box-gateway-deploy-add-shares.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ To create a share do the following procedure:
5757

5858
5. This step depends on whether you are creating an SMB or an NFS share.
5959

60-
- **SMB share** - Under **All privilege local user**, select **Create new** or **Use existing**. If you create a new local user, enter a **username** and **password**, and then **confirm password**. This action assigns the permissions to the local user. After you've assigned the permissions here, you can use File Explorer to modify these permissions.
60+
- **SMB share** - Under **All privilege local user**, select **Create new** or **Use existing**. If you create a new local user, enter a **username** and **password**, and then **confirm password**. This action assigns the permissions to the local user. Modification of share-level permissions is currently not supported.
6161

6262
![Add SMB share](./media/data-box-gateway-deploy-add-shares/add-share-smb-1.png)
6363

@@ -129,7 +129,7 @@ On your Linux client connected to your Data Box Edge device, do the following pr
129129
130130
> [!NOTE]
131131
> The following caveats are applicable to this release:
132-
> - After a file is created in the shares, renaming of the file isnt supported.
132+
> - After a file is created in the shares, renaming of the file isn't supported.
133133
> - Deletion of a file from a share does not delete the entry in the storage account.
134134
> - If using `rsync` to copy data, then `rsync -a` option is not supported.
135135

articles/databox-online/data-box-gateway-manage-users.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.topic: article
1010
ms.date: 03/25/2019
1111
ms.author: alkohli
1212
---
13-
# Use the Azure portal to manage users on your Azure Data Box Gateway
13+
# Use the Azure portal to manage users on your Azure Data Box Gateway
1414

1515
This article describes how to manage users on your Azure Data Box Gateway. You can manage the Azure Data Box Gateway via the Azure portal or via the local web UI. Use the Azure portal to add, modify, or delete users.
1616

@@ -19,17 +19,16 @@ In this article, you learn how to:
1919
> [!div class="checklist"]
2020
> * Add a user
2121
> * Modify user
22-
> * Delete a user
22+
> * Delete a user
2323
2424
## About users
2525

26-
Users can be read-only or full privilege. As the names indicate, the read-only users can only view the share data. The full privilege users can read share data, write to these shares, and modify or delete the share data.
26+
Users can be read-only or full privilege. As the names indicate, the read-only users can only view the share data. The full privilege users can read share data, write to these shares, and modify or delete the share data.
2727

28-
- **Full privilege user** - A local user with full access.
28+
- **Full privilege user** - A local user with full access.
2929
- **Read-only user** - A local user with read-only access. These users are associated with shares that allow read-only operations.
3030

31-
The user permissions are first defined when the user is created during share creation. After the permissions associated with a user are defined, these can be modified by using File Explorer.
32-
31+
The user permissions are first defined when the user is created during share creation. Modification of share-level permissions is currently not supported.
3332

3433
## Add a user
3534

0 commit comments

Comments
 (0)