Detailed Guide on Groups and Permissions on SharePoint Sites
Managing access in SharePoint is not just about granting users entry. It’s about ensuring the right people have the right level of control. By organizing users into groups and assigning them with necessary permission levels, you can maintain security, improve collaboration, and ensure seamless business workflow.
This article describes groups and permissions on SharePoint sites in SharePoint Server 2013/2016/2019 version.
Key Takeaways:
What Are Groups and Permissions in SharePoint Sites?
SharePoint groups refer to a set of users who can be managed together. A permission level is a set of permissions that can be assigned to a specific group for a specific securable object. Both SharePoint groups and permission levels are defined at the site collection level. They are inherited from the parent object by default.
Common Issues When Setting Groups and Permissions in SharePoint Sites
Challenges when setting groups and permissions in SharePoint sites:
- Complex permission inheritance structure
- Misuse of default SharePoint groups
- Risks of permission changes
- Inconsistent group naming conventions
- Duplicate or redundant groups
- Unclear ownership of permissions
Main Types of Groups and Permission Levels in SharePoint
The table below shows default groups created for team sites in SharePoint Server. Each default group gets assigned to a default permission level.
| Group Name | Default Permission Level |
|---|---|
| Visitors | Read |
| Members | Edit |
| Owners | Full Control |
| Viewers | View Only |
When using site templates other than the team site template, default SharePoint groups will differ. For example, the table below shows the other groups provided by a publishing site template.
There are also administrator groups for higher-level admin tasks. They include:
- Windows administrators
- SharePoint farm administrators
- Site collection administrators.
Permission Levels in SharePoint
By default, you can notice the following permission levels:
| Permission Levels | Description |
|---|---|
| View Only | View pages, list items, and documents |
| Limited Access | View specific lists, document libraries, list items, folders, or documents, with limited access |
| Read | Allows users to view items on the site pages |
| Edit | Add, edit, and delete lists; Can view, add, update, and delete list items and documents |
| Contribute | Add or change items on the site pages or in lists and document libraries |
| Design | View, add, update, delete, approve, and customize layout of site pages using browser/SharePoint Designer 2013 |
| Full Control | Includes all permissions |
Other permission levels which come with the publishing template by default:
- Approve – Permissions to edit and approve pages, list items, and documents.
- Manage Hierarchy – Permissions to sites and edit pages, list items, and documents.
- Restricted Read – Permissions to view pages and documents, but not historical versions or permissions information.
Common Permission Issues to Avoid in SharePoint
Common permission issues to avoid in SharePoint:
- Assigning permissions to users rather than groups
- Leaving orphan accounts with still-active access
- No permissions auditing following structural site changes
Manage Groups with the Right Permission Levels in SharePoint
On assigning the right permission levels, businesses can manage groups when using SharePoint Server 2013/2016/2019 version. Ensure to allot permissions properly in SharePoint Server for seamless business collaboration.
Frequently Asked Questions
1. How to recover or reset group permissions if access is accidentally removed on a company site?
If you have accidentally removed site permissions (for example, in SharePoint), get a site collection administrator involved immediately to get your access restored. You can recover the key by restoring Microsoft 365 groups within 30 days, resetting permission inheritance on libraries, or re-adding groups.
2. Best practices for managing access control on a team collaboration portal.
Effective access control on team collaboration portals requires enforcing the principle of least privilege, requiring multi-factor authentication (MFA), and using role-based access control (RBAC) to define permissions.
3. How do I configure user groups and permissions on a collaboration platform for business sites?
User group and permission configuration involves creating logical roles (Owners, Members, Visitors, etc.), assigning users to these roles based on their job function, and determining access levels (read, edit, full control) to secure data.
Leave A Comment