When I access my document library, I do not get a NEW button.
How do I troubleshoot this problem?
First determine the scope:
· Did it ever appear before?
· Does it appear for other users?
· Is it just this single document library or all libraries on this application?
Next, understand the requirements for the New button to appear:
· Use Client Integration Features permission must be enabled for the application in
Central Administration > Application Management > User Permissions for Web Application
· Client must not be authenticated with Forms Based Authentication.
· User must have permission to add items which is part of the CONTRIBUTE permissions template by default.
· The library must be configured to create something new:
· If you have Display "New Folder" command on the New menu enabled, it will expose the option to add a new folder under the New button dropdown menu.
· If you have at least one template URL configured it must point to a valid template. If you have more than one template URL configured, the dropdown menu obviously is longer.
Unfortunately, the NEW button does not interact with the client to determine if the appropriate application is installed before offering the option to create the document. For instance, the Create New Word document menu option appears even if no version of Word is installed on the client and then presents an error message when chosen, frustrating the users.
Maybe it isn’t broken but an intentional configuration. Here are two scenarios when you might not want the New button to appear:
· If you have a library where you only want documents to be uploaded.
· If you have significant number of users who do not have the necessary client applications installed.
· If you have a library which should only receive documents via email.
So, following the points above, to disable the New button across the entire application, remove the Use Client Integration Features permission from the application. To remove it at the library level, remove the template settings.
Credits: Thanks to Dan Holme for the email thread that started this thought process. You will find his blog at http://community.officesharepointpro.com/blogs/danholme/default.aspx.