In some cases, your site may contain content only meant for certain users or groups. For example, you may create a new library for a special project, and want to ensure that only people who work on that project can access the library.
Access can be granted or restricted. To restrict access, you have to break permissions inheritance, and then change the permissions for the list or library on a uniquely defined permissions page. Read below to learn more.
To restrict access to a list, remove the users or groups from the group that has permission to access the list. To remove users from a group, follow these steps.
The permissions page updates to show that the group or user no longer has permissions to the list.
Note: Make sure to leave Visitors as “Read Only.”
Note: For Site Owners and Site Collection Administrators:
DO NOT REMOVE "Style Resource Readers" Permission Group. If you find that this has been removed from your site collection, please contact APAN Support for assistance. Removing this, may cause permission related issues with your site collection, and sites that belong to the site collection.
“Style Resource Readers” should have read permission to "Master Page Gallery" and restricted read permission to the "Style Library" at the site collection level.
Again, if you need assistance with restoring these permission, please contact the APAN Help Desk ASAP.
To set permissions for an individual separate from the group he or she belongs to (e.g. “members”), start by clicking on on “People and Groups” in the Quick Launch bar.
The best way to control permissions within you site is to create permission groups. Without a permission group, you will have to change all of the affected users, when you change permissions. The following provides the steps involved in creating a permission group.
Anonymous access means that people without an APAN account will be able to see your APAN SharePoint
Using Anonymous Access is NOT recommended by APAN. This is not a good business practice, as anyone from any country can not only read/view the content, but also contribute and download what information that may be of interest to them. Use this feature wisely!
By default, all sites, lists, and libraries in a site collection inherit permissions settings from whatever is directly above them in the site hierarchy. This means a site inherits permissions from the root site of the site collection, and a sub-site inherits permissions from its parent site. A list inherits permissions from the site that contains the list. A list item inherits permissions from the list to which it belongs.
If the default configuration is not changed, permissions are inherited through the whole site collection. In a way, each element (site, sub-site, list, library, etc.) inherits permissions from the root site of the site collection.
If you break permissions inheritance for a list or library and then define new permission settings, the list (or library) becomes a parent for items in it. The items inherit the new permission settings (unless the items have uniquely defined permissions.
When you break permissions inheritance between a site, folder, list, library, list item or document and its parent you can restore inheritance at any time.