Lesson 1: Permission Fundamentals

💡 How to Check Your Permission Level

1. Go to your SharePoint site
2. Click the Settings gear (⚙️) in the top right
3. Look for "Site Permissions" - if you see this option, you're a Site Owner
4. If you don't see it - you have limited permissions and will need to request Site Owner access to manage permissions

⚠️ Important Note: If you're following this training but don't have Site Owner permissions, you can still learn the concepts. However, you'll need to request Site Owner rights from your IT department or current site owner to practice the hands-on exercises.

🎨 Additional Permission: Design

Who needs Design permission: Users who need to be approvers or edit templates (who are not site owners)

What Design permission includes:

• Everything from Edit permission
• Approve or reject content in approval workflows
• Edit site templates and master pages
• Modify site themes and branding
• Configure web parts and page layouts
• Manage site columns and content types at site level

💡 Best Practice: Manage permissions at the highest level possible. If everyone in your office needs access to the company policies, set it at the site level rather than individually on each document.

🎯 What Happens When You Break Inheritance?

1. Copy current permissions: SharePoint creates a copy of the inherited permissions
2. Stop automatic updates: Changes at higher levels no longer affect this item
3. Enable custom control: You can now add, remove, or modify permissions independently
4. Create unique access: Set different permission levels for specific users or groups

1. Navigate to the item: Library, folder, or file you want to secure
2. Access permissions: Click the "..." menu → Manage Access
3. Stop inheriting permissions: Click "Stop inheriting permissions"
4. Modify access: Add/remove users, change permission levels
5. Test access: Verify the permissions work as expected

🚨 Unique Permissions Are NOT Best Practice

Unique permissions should be avoided in most scenarios and used only when absolutely necessary. They become exponentially more complex and unmanageable as organizations grow.

Major Issues in Large Organizations:

• Exponential complexity: Each unique permission creates a management burden that multiplies across thousands of items
• Performance degradation: Sites with many unique permissions become slower and less responsive
• Security vulnerabilities: Forgotten unique permissions create unintended access paths
• Audit nightmares: Nearly impossible to track and report on access across large organizations
• User confusion: Inconsistent access patterns frustrate users and reduce productivity
• Administrative overhead: Requires constant monitoring and maintenance by IT teams

💡 Strict Best Practice Rules:

• Minimize usage: The less broken inheritance you have, the better - avoid whenever possible
• Document everything: Every unique permission must have business justification
• Regular audits: Monthly reviews to remove unnecessary unique permissions
• Prefer alternatives: Use separate sites or libraries instead of breaking inheritance
• Monitor closely: Set up alerts for new unique permissions

💡 Essential Monitoring Requirements: Implement strict governance around unique permissions:

• Monthly audits: Review and justify every unique permission
• Documentation: Maintain tracking system for location, reason, owner, and review date
• Approval process: Require management approval before breaking inheritance
• Quarterly cleanup: Actively remove unnecessary unique permissions
• Growth monitoring: Set alerts when unique permissions exceed safe limits