This project is read-only.
SharePoint support engineers, administrators and application developers frequently encounter incidents reported by users related to site access. Many a times these are as simple as the user not having adequate permissions on the site; and at the same time it must be acknowledged that this can prove to be a nightmarish challenge in those environments where security permissions are individually assigned to securable objects, breaking security inheritance from the parent site.

Support Engineers/Application Developers:
SharePoint support engineers most of the time receive issues related to SharePoint is not accessible. This could happen due to lack of appropriate permissions. For resolving those types of issues, support engineers have to look at:

1. Security permissions on the site/library/object that the user is not able to access.
2. SharePoint all users list to see whether the user is available in the list that has access.
/* Note: Access issues are dependent on permissions. For example: users included in the default Visitors group have only ‘Read’ permissions. */
3. SharePoint all groups list to see whether the group contains required users which ensure that users are available in the right group.
4. Check what type of roles (like Full Control, Contribute, etc.) is assigned to a particular group.
5. Check whether particular user has assigned to all required SharePoint groups.

SharePoint Administrators:
Administrators have to maintain and control access permissions to all users and SharePoint groups for site collections. Administrators generally receive requests for doing following activities.

1. Create/Delete different SharePoint groups and assign appropriate roles to them.
2. Add/Remove users to the appropriate SharePoint groups.
3. Add/Remove roles to the appropriate SharePoint groups.

Last edited Jun 7, 2011 at 10:40 AM by arunpnair, version 3