Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
organisationcloud:useraccesscontrols [2024_02_28 01:03] – external edit 127.0.0.1 | organisationcloud:useraccesscontrols [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== User Access Controls ====== | ||
- | |||
- | For more information see [[: | ||
- | |||
- | \\ \\ This section of the Wiki outlines managing access control for Cloud File Server users.\\ \\ Can be used with:\\ \\ - Cloud File Server hosted users\\ - Cloud File Server IaaS users\\ - Cloud File Server on-site Appliance users | ||
- | |||
- | ===== 1 Shared Folder Permissions ===== | ||
- | |||
- | {{:/ | ||
- | |||
- | The Cloud Administrator can set Access Control permissions for any shared Team Folder, or sub folder, for any user on any Storage Cloud that has been designated as a shared folder (shared folders are created from the NAA Web File Manager. See [[organisationcloud/ | ||
- | |||
- | The default settings when a folder is shared are that users have no access to a shared folder ie. it is permissive by default. | ||
- | |||
- | Shared Team folders can be mapped to any nominated Cloud folder, such as folders on Google Drive,, DropBox, OpenStack, Amazon S3 etc. This enables access control to be maintained above different information Clouds as long as users do not have direct access to the mapped Cloud. | ||
- | |||
- | |||
- | ===== 2 Setting Permissions on Folders ===== | ||
- | |||
- | |||
- | |||
- | {{:/ | ||
- | |||
- | Setting access permissions can work in two ways, the first is by applying permissions on the folder. Access permissions set to the folder designate how any user or role is able to interact with the folder, other than the Cloud Admin role.\\ \\ If 'No Access' | ||
- | |||
- | |||
- | ===== 3 Setting Permissions against users ===== | ||
- | |||
- | {{:/ | ||
- | |||
- | Assigning permissions on a per user basis is the second method that can be used to designate access control. | ||
- | |||
- | If "No Access" | ||
- | |||
- | **Note:** If multiple permissions are set then there is a hierarchy for how permissions are used. user over-rides role and role overrides Folder permissions. | ||
- | |||
- | **Next Section:** [[governance|Governance and Compliance]] | ||
- | |||
- | |||