Presentation is loading. Please wait.

Presentation is loading. Please wait.

SharePoint 2010 Permissions Keith Tuomi. profile KEITH TUOMI SharePoint Consultant / Developer at itgroove Developing Online Systems since 1991 10 years.

Similar presentations

Presentation on theme: "SharePoint 2010 Permissions Keith Tuomi. profile KEITH TUOMI SharePoint Consultant / Developer at itgroove Developing Online Systems since 1991 10 years."— Presentation transcript:

1 SharePoint 2010 Permissions Keith Tuomi

2 profile KEITH TUOMI SharePoint Consultant / Developer at itgroove Developing Online Systems since 1991 10 years as dedicated.NET/Microsoft Developer 110% SharePoint focused for 7 months, with no looking back Blog TwitterWeb

3 - Permissions - single units of access that represent specific tasks that can be performed at the list, site, or personalization level - permission levels are made up of sets of permissions - SharePoint ships with a core list of permissions that cannot be edited, added to or deleted - Users - smallest value to which access can be granted - value corresponds to an account in Active Directory or another host application for user accounts - Groups - a set of users who will have identical access needs - Securable objects - levels within SharePoint 2010 that can be “ locked down,” or secured, by setting specific user access - Inheritance - used to describe how user access is created by default within SharePoint - Security Trimming & Indexing - SharePoint will only show you search results for content you have access to, and for which SharePoint understands the security - Audiences - Used to target content to specific sets of users - Defined in the User Profile Service Application in Central Admin - NOT a security setting but simply a way to display pertinent content to specific users Access Management Terminology

4 Topology Web Application

5 - Permission Levels are collections of permissions - level of access that users with the assigned permission have is based on the permissions that make up the permission level. - Defined at the site collection - Managed by Site Collection Administrators - Customize an existing permission level - Copy an existing permissions level and edit the copy - Create a new permission level “ from scratch” Permission Levels

6 Default Permission Collection Permission LevelDescription Full Control -Contains all permissions. -Assigned to the Owners SharePoint group, by default - cannot be customized or deleted. Design - Can create lists and document libraries, edit pages and apply themes, borders, and style - Not assigned to any SharePoint group, by default. Contribute - Can add, edit, and delete items in existing lists and document libraries. - Assigned to the Members SharePoint group, by default. Read - Read-only access to the Web site - Assigned to the Visitors SharePoint group, by default. Limited Access - Designed to be combined with fine-grained permissions to give users access to a specific list, document library, item, or document, without giving them access to the entire site. - To access a list or library a user must have permission to open the parent Web site and read shared data such as the theme and navigation bars of the Web site. - Cannot be customized or deleted. - You cannot assign this permission level to users or SharePoint groups, instead, SharePoint automatically assigns this permission level to users and SharePoint groups when you grant them access to an object on your site that requires that they have access to a higher level object on which they do not have permissions. F or example, if you grant users access to an item in a list and they do not have access to the list itself, SharePoint automatically grants them Limited Access on the list, and also the site, if needed.

7 - Central Administration > Manage Web Applications - Configures policy-based access to all content in a web application - Allow and Deny - Deny overrides any allow permissions - SharePoint 2010 allows you to define policies for any available permission Web Application Policy

8 - Site Actions > Site Permissions - Groups are established at the site collection - Can be given permissions at the site level - Permission inherits down from there - When you create a group you do not have to assign a permission - A group without a permission at the site can still be assigned permissions to another securable object - Create a sub-site - Unique or Inherited Permissions Site Security

9 - Owners: Full Control - Visitors: Read - Members: Contribute - Features add more groups (Designers, etc.) - The Members group is the “ default members groups” Default Groups

10 - Enable hierarchical membership management - Create a group named Site Managers > owned by site collection administrators > membership managed by owner (site collection administrators) - Site members (and other groups) > Owned by Site managers > Membership managed by owner (Site Managers) - Enable Access Requests - Add link to request page for the group - Optionally enable auto-accept of access requests - Control Member Visibility SharePoint Groups

11 - Active Directory - Technical user interface (AD Users & Computers) - No provisioning (requests, workflows) - Difficult delegation of membership management - Centralized security (group membership) management - SharePoint - Non-technical user interface - Easy delegation of group membership management - Optional provisioning of membership requests - Unified view of SharePoint groups & users - Only applies to SharePoint Group Management Comparison

12 - Assigning permissions directly to AD groups - Possible but not recommended > Assumes that content will always be hosted in a web application using AD as its authentication provider - Nest Active Directory groups in SharePoint groups - Add to a SharePoint group and give permissions (recommended) > user > Active Directory group > SharePoint group - Must be a security group (not a distribution group) > Distribution groups are expanded and then must be kept in sync - Distribution groups can be used to create audiences Using Active Directory Groups

13 Users > Active Directory Group > SharePoint group - Ideal world: Synchronization of membership between Active Directory and SharePoint groups -“ Intranet” sites: AD groups  SP groups to define access - Add site to users ’ My Sites with personalization site links - Support easy management of access - Add site to users ’ My Sites with personalization site links - “ Collab” sites: Add users directly to SP groups - Provide My Site visibility - Provide visibility of user in user information list - Provide visibility to site owners and members - Support collaboration To Nest or Not to Nest

14 - List > List Settings / Library > Library Settings - Stop Inheriting Permissions - Copies inherited permissions as initial explicit permissions - Can reset with Inherit Permissions button - Ribbon Actions for Selected Group(s)/user(s) - Grant Permissions - Remove User (or group) Permissions - Edit User (or group) Permissions - Check permissions: Resultant set of permissions - Anonymous Access List & Library Permissions

15 Items & Documents will be referred to in this presentation as “ Items” unless specific difference needs to be highlighted - Change permissions on a folder or item - Item > Arrow > Manage Permissions - When viewing the item properties in SharePoint > Edit Permissions Folder & Item/Document Security

16 - Permissions (role assignments) are inherited from the parent object - Inheritance can be broken - All permissions are explicit - Any changes to parent do not affect the child object - Inheritance can be reinstated - All customizations (explicit permissions) are lost - Use inheritance wherever possible - Simplicity, coherence, maintainability Inheritance

17 - SharePoint access is based on a per URI (web address) basis - The permission to the URI is all that matters - These kids are wild: no need to ask the parents permission - No equivalent to NTFS (Windows folder security) Traverse Folder permission - Explicit Inherited - One or the other - Different than NTFS (inherited + explicit) - Check Effective Permissions button - Shows you the actual effective permission level Effective Permissions

18 - The SharePoint interface and search results are security-trimmed - User don ’ t see what they do not have permission to read - Item-level permissions on pages in a Page Library - Problem: A Web Part displays items > Users don ’ t see items they don ’ t have access to > The crawler sees all items in the web part and indexes them - When inheritance is stopped within a site, all Web Part content on ASPX pages is not indexed by default - Site Settings > Search and Offline Availability > Indexing ASPX Page Content Security Trimming & Indexing

19 Permission Levels Publishing Feature Collection - Available only with Publishing Features turned on Publishing Feature Manage Hierarchy Restricted Read Approve

20 - Columns can not be secured uniquely (out of the box) - Performance - Conditional formatting - Related Lists - Third party solutions - Audiences - Make content visible to users - Effect can be close to security, but it is not security SharePoint Security Notes

21 - In-place records management - New in SharePoint 2010 - Record library still supported for dedicated record libraries - Enable the feature at the site collection level - Declare records management attributes - Site Collection - F older - Content type - Supports security at the document level without permissions - Information rights policies - Relies on Active Directory Rights Management Services Information Management Policies

22 - Remember: limited access is for SharePoint to manage unique permissions. It neither means someone is limited to access something, nor does it mean they have limited access to something. Ignore it - Permissions can be defined at creation of a site (more options) but can ’ t be during creation of a new list or library (in the GUI at least) - When in doubt, check effective permissions - Help your users, set a valid email account for ‘ manage access requests ’ - Finally, build sites based on a ‘ team ’ of people. Setting individual permissions shouldn ’ t be something you do all the time, it should be in the ‘ odd times needed ’ not the goto action Conclusion

Download ppt "SharePoint 2010 Permissions Keith Tuomi. profile KEITH TUOMI SharePoint Consultant / Developer at itgroove Developing Online Systems since 1991 10 years."

Similar presentations

Ads by Google