--- title: "Managing Shares" slug: "managing-shares-20" tags: ["8.2", "Portal"] updated: 2024-12-30T16:40:43Z published: 2024-12-30T16:40:43Z canonical: "kb.ctera.com/managing-shares-20" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.ctera.com/llms.txt > Use this file to discover all available pages before exploring further. # Managing Shares Manage the edge filer from the portal has been changed to match the edge filer procedure. 1. Select **Main > Devices** in the navigation pane. The **Devices** page opens, displaying all the devices registered to the portals. ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-BJP2719T.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A33%3A37Z&se=2026-11-11T05%3A33%3A37Z&sr=c&sp=r&sig=muh9Ax%2FKDTJYJ4Gzcq5UqaLFoTvhWcZdZUVDzGQCv3o%3D) 2. Click the device name. A message can be displayed that you will be redirected to the portal view for the selected device. In this case, click **CONFIRM**. The device details are displayed in a new browser window. ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-RVGEGXCX.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A33%3A37Z&se=2026-11-11T05%3A33%3A37Z&sr=c&sp=r&sig=muh9Ax%2FKDTJYJ4Gzcq5UqaLFoTvhWcZdZUVDzGQCv3o%3D) The details are different for each type of device and whether the device is currently connected to the portal. 3. Click the **Shares** tab. 4. Click **New Share**. The **Select a Folder to Share** wizard opens, displaying the volumes and folders on the gateway. 5. Select the volume, folder, or subfolder on which you want to define the share. **Note** Subfolders, nested shares, are **not** available for Cloud Backup. - To create a new subfolder to select as a nested share, select the parent folder, click **New Folder**, and then assign the subfolder a name. - You can define nested shares based on subfolders within your own cloud drive, which are available to users based on the permissions defined when creating the share. If the share has NT ACL settings, these settings are applied to the nested share and to every share below this share. For example, if the administrator has a personal cloud drive named *MyGateway*, to which he migrated a full old Windows File Server with the following structure: ``` /Cloud /WIN-File-Server /Share1 /Share2 /My Files /Shared with me ``` If, before the Windows File Server migration, `\\Win-File-Server\Share1` and `\\Win-File-Server\Share2` shares were exposed in the old file server, users logged in to MyGateway can access the content of the shares: `\\MyGateway\Share1` and `\\MyGateway\Share2` after they are defined: ``` Share1 = \\MyGateway\Cloud\WIN-File-Server\Share1 Share2 = \\MyGateway\Cloud\WIN-File-Server\Share2 ``` 6. Click **Next** and then assign the network share a name. 7. Click **Next** to choose through which sharing protocols to expose this share. The **Sharing Protocols** window is displayed. ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-FQKUU3DM.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A33%3A37Z&se=2026-11-11T05%3A33%3A37Z&sr=c&sp=r&sig=muh9Ax%2FKDTJYJ4Gzcq5UqaLFoTvhWcZdZUVDzGQCv3o%3D) **Windows File Sharing** is checked by default and cannot be deselected. From the drop-down, select one of these access levels for the share: **Client Side Caching** – Server files are designated for off-line work so that a copy of the files is cached on the client computer and can be accessed when the client is off line in exactly the same way as if they were stored on the Windows file server. - **Only Authenticated Users**. Users will be required to authenticate using their gateway user name and password, in order to access the network share. - **Windows ACL Emulation Mode**. The share will be a Windows ACL emulation mode share. Users access the shared files and folders through standard Windows client computers; for example, using Windows Explorer through the SMB/CIFS access provided by the edge filer. Windows ACL Emulation Mode also allows you to block users from writing specific file types into the gateway share or gaining control of the content located on it. - **Manual caching for documents** – Users must cache files manually. - **Automatic caching for documents** – A copy of the files is cached automatically. - **Disabled** – The client computer cannot cache files locally and the updated copy must be retrieved from the file server. 8. Specify how you want to share the files. **FTP** – Users will be able to access and download files on this share from the FTP site. To configure the FTP server, go to **Shares > FTP Server**. 9. Click **Next**. The **Block File Types** window is displayed. ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-KNVSH6YN.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A33%3A37Z&se=2026-11-11T05%3A33%3A37Z&sr=c&sp=r&sig=muh9Ax%2FKDTJYJ4Gzcq5UqaLFoTvhWcZdZUVDzGQCv3o%3D) 10. Check **Enable Blocking File Extensions** to block file extensions. Enter the file extensions per user and group: 1. In the Local Users drop-down list, select one of the following: **Local Users** – Search the users defined locally on the CTERA Edge Filer. **Domain *domain* Users** – Search the users belonging to the domain called *domain*. **Local Groups** – Search the user groups defined locally on the CTERA Edge Filer. **Domain *domain* Groups** – Search the user groups belonging to the domain called *domain*. 2. In the **Quick Search** field, type a string that is displayed anywhere within the name of the user or user group you want to add, or click **...** to list the users. A list of users or user groups matching the search string is displayed. 3. Select the user or user group in the table. The user or user group is added to the list of users and user groups for who, you want to block some file extensions. 4. For each user and user group, click in the **Extensions** field, and then specify the extensions to block, with each extension separated by a comma (,). List only the letters of each file extension. For example, to block EXE files, list the `exe` file extension; to block PDF files, list the `pdf` file extension. To block both EXE and PDF files, list them as `exe,pdf`. Blocked extensions are not case sensitive. Wildcards (for example, `*.exe`) are not supported. 11. Click **Next**. The **NFS (UNIX File Sharing)** window is displayed. ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-SJX5V5KG.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A33%3A37Z&se=2026-11-11T05%3A33%3A37Z&sr=c&sp=r&sig=muh9Ax%2FKDTJYJ4Gzcq5UqaLFoTvhWcZdZUVDzGQCv3o%3D) 12. Check the **Enable NFS Access** option to enable NFS clients to access the share. ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-ZGJYL8XG.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A33%3A37Z&se=2026-11-11T05%3A33%3A37Z&sr=c&sp=r&sig=muh9Ax%2FKDTJYJ4Gzcq5UqaLFoTvhWcZdZUVDzGQCv3o%3D) **Note** For a windows ACL emulated share, permissions are written differently when NFS access is enabled and when it is not enabled. If you have a standard windows ACL share with permissions and then turn on NFS, the NTACL permission are no longer readable and need to be reapplied. This applies for any device the data is shared on. Because the permissions synced, if a share doesn’t match NFS enablement across devices, the permissions will be unreadable across devices as data is synced.: Either have **every** device referencing the share be NFS access enabled or not. Either, click **New** to configure each client to which you want to grant access. A row is displayed in the table: Or, Click **Remove** and then select the client's IP address to remove the client from the list. **Note** The NFS mount path for the network share is specified at the top of the window. 1. Enter the client's IP address and netmask in the appropriate fields. 2. Select the permitted level of access to the network share via NFS. Options are **None**, **PreviewOnly**, **Read** **Only**, or **Read/Write**. **Note** Preview Only permission prevents downloading, copying, or printing the file and content cannot be synchronized for offline access. For full details, refer to the [Team Administrator Guide](/v1/docs/team-administrator-guide). 13. Click **Next** and set which users can access this network share. 1. In the **Local Users** drop-down list, select one of the following: **Local Users** – Search the users defined locally on the gateway. **Domain** *domain* **Users** – Search the users belonging to the domain called *domain*. **Local Groups** – Search the user groups defined locally on the gateway. **Domain** *domain* **Groups** – Search the user groups belonging to the domain called *domain*. 2. In the **Quick Search** field, type a string that is displayed anywhere within the name of the user or user group you want to add, or click ... to list the users. A table of users or user groups matching the search string is displayed. 3. Select the user or user group in the table. The user or user group is added to the list of users and user groups who should have access to the network share. 4. For each user and user group, click in the **Permission** field, and then select the access level from the drop-down list. 14. Click **Next** and then **Finish** to complete the wizard. Click ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-VI7U4Q86.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A33%3A37Z&se=2026-11-11T05%3A33%3A37Z&sr=c&sp=r&sig=muh9Ax%2FKDTJYJ4Gzcq5UqaLFoTvhWcZdZUVDzGQCv3o%3D) next to the share to edit it or remove it.