SharePoint is widely used for storing and maintaining content. Different groups of users access SharePoint, but what if an organization wants to provide granular customized access rights like read, write or delete for different users? In this tip, we cover how this can be accomplished.
There are situations when we need to provide access to a SharePoint site for users that are external to our domain. They could be clients, partners or vendors. We do not want to add these users to our Active Directory, so NTLM authentication is not an option, but still we need to somehow provide them access to certain areas on our SharePoint site.
There is a company with a lot of employees. The requirement is to automate the request and approval process for employee holidays. Each employee has to be able to submit requests for holidays. The request has to be approved or rejected by the employee's manager. Each employee has to have the ability to view only his/her requests. Each manager has to have the right to approve or reject only requests that are requested by employees in his/her department. After the manager's actions, the manager has to be able to only read requests related to his/her department.
As SharePoint system administrator, I create all sites for users. This is true even when I turn over "Full Control" to a power user that will design and maintain the site, including setting up permissions. However, I still get the automated email messages from users that "request access" using the built-in access request form. Is there a way I can direct these email messages to go the power user in charge of the site?
It's easy to find blogs and msdn documentation on creating Custom Timer jobs, but still developers face issues while deploying and running them on SharePoint farms due to lack of timer job development guidelines.
Even with complete read and write access to a SharePoint list or library with a 'People or Group' field type, the user gets the message "The control is not available because you do not have the correct permissions. This puzzled me for a few minutes, but soon I had the solution...
If you run a "portal" site for an organization, you need to ensure that the information on the home page is meaningful and relevant for your users, so they keep coming back. But this becomes difficult when you have a large and diverse user base. For example, the Sales department will find information about new lines in promotional goods riveting, but it will have no interest for engineering. Conversely, engineering will be excited by news about a breakthrough in material bonding, but it will be gobbledegook to the accounting department.
One option would be to include all the information on the page that anyone would be interested in. This will produce a large and "busy" page, which users will find unattractive and hard to use.
I am just getting started with SharePoint and noticed many security options and features. I can see that you can attached named users to sites, lists and libraries. I can even see there is some type of grouping system. But I don't know what to make of it all.
You have a mature SharePoint 2007 installation, but lets say you have not been able to update it... And then one day, you get "the call". (And the sky is falling, of course!)...
...The Helpdesk has just informed you that all users are getting the following error when attempting to access one or more site collections.
"Attempt to release mutex not owned by caller. (Exception from HRESULT: 0x00000120)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ApplicationException: Attempt to release mutex not owned by caller. (Exception from HRESULT: 0x00000120)"
A SharePoint web application can potentially contain thousands of site collections. Granting or denying uniform access to all of those site collections for a set of users can be difficult to apply and manage.