This document discusses SharePoint administration and permissions. It describes the different levels in the SharePoint hierarchy from the farm down to individual items. It explains the different groups and permission levels that can be applied at each level, such as site collection administrators and the Visitors, Members, and Owners permission levels. The document provides recommendations for planning and managing permissions and security groups to balance centralized control with visibility and ease of administration.
Introduction to SharePoint Administration and permissions by Craig Jahnke, dated November 20, 2014.
SharePoint 2013 architecture includes Server, Shared services, Web applications, Sites, Document libraries, and Individual items.
Levels of SharePoint administration: Server/Farm Level, Shared services, Web application, Site Level, and specific roles like administrators and owners.
Site permissions outline user abilities, fine-grained permissions on objects, SharePoint Groups, and securable objects.
Details on permission levels available in SharePoint for Sites, Libraries, Folders, Documents, and Items.
Best practices for site permissions: follow the principle of least-privileged and use standard groups for roles.
Specific roles: Visitors (read-only), Members (contribute), and Owners (full control with limitations on number).
Detailing various permission levels in SharePoint from View Only to Full Control, each defining user capabilities.
Additional permissions for publishing templates, including Approve, Manage Hierarchy, and Restricted Read.
Exploring the connections and relationships among the various permission levels within SharePoint.
Benefit of using SharePoint groups for managing user permissions efficiently, including overview of AD DS groups.
Pros of security groups in SharePoint include centralized management, automatic updates, and no manual user management post-setup.
Cons of security groups include limited visibility of user activities and individual user tracking until contribution.
Recommendations for using security groups versus direct user addition based on site accessibility and stability needs.
A summary of the site permissions layout in SharePoint.
Information focusing on managing people and groups within the SharePoint environment.
Encouraging that you are now recognized as a SharePoint Security Superhero.
SHAREPOINT 2013 LEVELS
Server or SharePoint farm
Shared services
Web application
Sites
Document library or list
Individual items
3.
LEVELS OF ADMINISTRATION
Server Farm Level
Farm Administration group
Window Administration group
Shared services level
Service application administrators
Feature administrators
Web application level
No unique group
Site Level
Site Collection administrators
Site Owners
4.
SITE PERMISSIONS
Permissionsgrant a user the ability to perform specific
actions.
Fine-grained permissions are unique permissions on
securable objects that are at a lower level in a site
hierarchy.
SharePoint Groups is a group of users who are defined
at site collection level for easy administration of
permissions.
User is are a person with a user account from any
authentication provider supported by the Web
application
Securable Objects is a site, list, library, folder,
document, or item for which permissions levels can be
assigned to users or groups
PLANNING FOR SITEPERMISSIONS
Follow the principle of least-privileged
Use standard groups
Visitors
Members
Owners
Use Permission levels instead of assigning
individual permissions
7.
PERMISSION LEVELS
Visitors
Read only access
Can see pages and items and open documents
Cannot add or remove content
Members
Can contribute by adding or removing items
Cannot change structure, settings, or appearance
Owners
Limit the number of people
Can change structure, settings, or appearance
8.
AVAILABLE PERMISSION LEVELS
View Only Includes permissions that enable users to view
pages, list items, and documents.
Limited Access Includes permissions that enable users to
view specific lists, document libraries, list items, folders, or
documents, without giving access to all the elements of a site.
You cannot edit this permission level directly.
Read Includes permissions that enable users to view items on
the site pages.
Edit Includes permissions that enable users to add, edit and
delete lists; can view, add, update and delete list items and
documents.
Contribute Includes permissions that enable users to add or
change items on the site pages or in lists and document libraries.
Design Includes permissions that enable users to view, add,
update, delete, approve, and customize the layout of site pages
by using the browser or SharePoint Designer 2013.
Full Control Includes all permissions.
9.
AVAILABLE PERMISSION LEVELS–
PUBLISHING TEMPLATE
Approve Includes permissions to edit and
approve pages, list items, and documents.
Manage Hierarchy Includes permissions to sites
and edit pages, list items, and documents.
Restricted Read Includes permissions to view
pages and documents, but not historical versions or
permissions information.
SHAREPOINT & SECURITYGROUPS
You can manage users of SharePoint sites more
efficiently if you assign permission levels to groups
instead of to individual users.
A SharePoint group is a set of individual users and can
also include Active Directory Domain Services (AD DS)
groups.
In AD DS, the following groups are commonly used to
organize users:
Distribution group - A group that is used only for e-mail
distribution and that is not security-enabled. Distribution
groups cannot be listed in discretionary access control lists
(DACLs), which are used to define permissions on resources
and objects.
Security group - A group that can be listed in DACLs. A
security group can also be used as an e-mail entity.
12.
SECURITY GROUP PROS
Provides centralized management of groups and
security.
The security group is the only place where you
manage individual users.
Once you add the security group to a SharePoint
group, you do not have to manage security group
members in that SharePoint group
If a user is removed from the security group, the
user will be automatically removed from the
SharePoint group.
13.
SECURITY GROUP CONS
Do not provide full visibility of what is occurring.
User Information List will not show individual users
until they have contributed to the site.
When a security group is added to a SharePoint
group for a specific site, the Site will not appear in
the users’ My Sites.
14.
RECOMMENDATIONS
For intranetsites that are broadly accessed by your
users, use security groups because you do not care
about the individual users who accessed the
intranet site home page.
For collaboration sites that are accessed by a small
group of users, add users directly to SharePoint
groups.
For easier permission management, security
groups should be:
Large and stable enough that you are not continually
adding additional security groups to your SharePoint
sites.
Small enough that you can assign appropriate
permissions.