I have the requirement to allow users to view the content of a document library, including browsing through folders, but not actually open the individual files.
There doesn't appear to be a permission to restrict users from opening files, but still display the item.
Naturally it is an option to create a view that doesn't have the 'open link' in it, but that doesn't stop users from manually constructing the URL. Also there are other options in the context menu that I want to be available for the individual documents.
I realise that a similar question has been asked before.
I solved a similar issue a while back ago by creating a custom Web Part that used RWEP to show the contents of a doc lib.
I don' think its anything out of the box for your problem. The closest thing you could do is to have the document moved to a different library and linked to the item (could achieve some customization for this using a workflow) then you give the users read only to the lists and no access to the document library. just a thought :)
I think Information Rights Management might allow you to restrict certain groups of users from opening files within a specific document library.
(this link is aimed specifically at SP2010, but may be of info for a possible solution or direction for you) Information Rights Management in SharePoint Foundation
that have been replaced. A small amount of luck is that an administrator will specify which new document should ‘replace’ an existing document from the originals. Over time I would be required to add more...I have 2 users, Martin and John I have 5 documents, all available to Martin and John. I also have 2 documents that are available to John only (Martin must not see them). To complicate matters... on each individual document; I could add and remove these roles depending on whether Martin or John should be able to see that document. I think this would get really, really complicated. What other
User Steven has the Active Directory account however his profile is not yet populated into SSP User profiles. NT Authenticated users have the access permission on "Shared Documents - Document Library". So, will Steven be able to access the "Shared Documents"? I guess, IIS will authenticate the user Steven to access the "Shared Documents" and SharePoint will authorize the user to View the items in "Shared Documents", is that right?
to them by SharePoint as read-only (so they will get the above error message). However, often they are demonstrably the only user to have accessed the document - in fact, sometimes this will happen... that user opening it may get it returned to them as read-only, often other users, even multiple other users, can click the button and the spreadsheet will open for them in edit mode! Questions: What is causing this behavior? I can change the code to avoid it if I can figure out why it is happening. Is there any way through the SharePoint UI or APIs to "release" the document so that the original
I have a document library using a document set content type. I can create a new document set through the UI and it works perfectly. I'm now trying to create a document set in this library... for the set looks like a folder instead of the document set icon clicking on the document set doesn't show the document set home page, it just behaves like a normal document library running CAML queries shows that both internal fields HTML File Type and ProgId should be SharePoint.DocumentSet but instead they are blank changing a field value on the document set folder doesn't propogate to its contents
I have a document library which contains some Word documents that I'm trying to copy down to my local disk. I've opened the document library using Windows Explorer, and am dragging the individual files from that window to a folder on my local PC. Some files work, but others are giving me this error (on Windows 7 x64): The file name you specified is not valid or too long. Specify a different...? I can't for the life of me determine why some files are throwing this error while others are copying just fine. UPDATE The files copy without any problem if we go into the doc lib's settings
We have a SharePoint 2007 deployment which will have a substantially large document library. My client wants the ability to export this library to an Excel spreadsheet, but specifically wants... to Spreadsheet, but it does not appear to support automated subdivision of the list items into separate worksheets. I do not know if Excel Services that come with MOSS are capable of it, but we do not have MOSS so we cannot consider it an option for now. EDIT It seems that by mentioning "out-of-the-box", I am implying that I'd prefer something quick and simple. Let's dispel that. I do a lot
When we open a PDF in the browser from a document library, and then press the back button we get page expired. One possible solution we have found is to open the PDF in adobe reader, as per this post. Is their a way to solve this that does not involve changes to the registry on the client.
appropriately. I can see the status change on the Solution Management page from deploying to deployed. There are no errors in the trace logs or event viewers. However, the 12 hive only contains files... added another server to the farm, moved the central admin with the stsadm tool, and removed the old server from the farm. Here is what I have tried: Deployed to two other farms: successfully deployed..., we were lucky enough to still have the soon to be decommisioned server that previously ran Central Admin (Server1). So, I added the server to the farm. Removed the Central Admin from the new Server
for only the doc lib they have access to, and not the other customer's webparts? If I put them all on the home page, the user will get a message stating they don't have permissions to view the data... with, my customer wants to allow her customers to log in to simply swap files with her. Of course each customer should only see their own files. Also, my customer wants SharePoint to be themed to match her website. Since we're starting off with the basic package I cannot install my own custom WSPs to handle this, instead I have to rely on SPD and out of the box SharePoint functionality. My issue