What feels like an NP-Complete problem, managing document access depending on a users permissions

  • What feels like an NP-Complete problem, managing document access depending on a users permissions Rob

    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 these documents should replace 2 of the existing documents from the original 5 - so that only 5 documents are ever displayed to Martin or John.

    John must not be able to see the original 2 documents 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 documents and and users, providing the same functionality of ‘replacing’ certain documents for certain users.

    How would you do this?

    My first thought was creating roles and configuring the roles 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 approach could I try?

    Any solution has to be security trimmed for the all important search function!

2007 permissions document
Related questions and answers
  • I have an InfoPath form that starts a workflow (on item created). The business requirement is that after submission form must be read-only (no changes to the initial request can be made). However workflow must change certain properties of the form (e.g. approval time, approval phase etc.). By default SharePoint workflows run under initiator account, however I am wondering would you recommend creating an event handler that is going to kick start a workflow under system account. Workflow would than be able to revoke all the contribute privileges but still be able to update the form during

  • or automatic creation of an accident list item. Now the process will need to have a set of official forms filled in by various people. This is where I find SharePoint limiting me with it's document centric... the user find other related documents generated in the workflow. I find that all this rapidly gets messy in trying to retrofit this different type of workflow into SharePoint. There are ways and means but I can't find anything ideal, or even just something I'm semi happy with. I'm hoping that people could answer with ways they can think of for using a workflow to drive further document creation

  • have 11 pages of document links, each with its own subheadings. So far I have it set where each document has a custom field called "Page" with a check box list of all the document pages on the intranet site. On each individual page, I have setup a Content Query Web Part that displays the documents that have the corresponding Page value set (i.e. if a document Page value has been checked for "HR... the documents into their subheadings once they are on the appropriate page. I could create individual check boxes for each page/subheading combination, but this would create a list of approximately 50-75

  • 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

  • it to the default.aspx home page. I would be happy either way. Note: I want to be able to activate this on existing site, I dont want to create a new Site Definition. Here is what I have tried: Feature Receiver... because I think its a critical limitation that will cause me grief in future solutions too. Here is the scenario. I have an existing site and I want to be able to activate a feature...), then there doesn't seem to be a way to just get a reference to the page, it always wants to overwrite it with a new file. But I dont want to do that, I just want to add a Web Part to the existing page. See my

  • I have a Silverlight 4 Beta application where I'd like to use the SharePoint object model to upload a document to a SharePoint site - should be simple enough, except an exception is thrown at: using (SPSite siteCollection = new SPSite(siteCollectionUrl)) The Web application at http://intranet.fabrikam.com could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application. This particular exception is actually really well documented

  • A common issue with my customers is that they define a number of content types that should be available on a document library. That library is part of a custom site template and pretty soon we'll have 200 sites using that template. Now the customer realize that they need two new content types on that library. Oh, and they will need those content types on the existing sites as well. I might have misunderstod something about content types or just misconfigured the library, but so far the only way I have been able to add those new content types on existing sites have been through a powershell

  • I recently authored a C# based script for a blog posting, which copies column data from one file to another. While testing this solution I noticed that copying this data works differently depending... to write the destination file, iterate through all fields of the source file and then update the destination file again. If I treat all documents the same then either meta data is not copied over, depending on the file type, or certain column types are not copied over (e.g. DateTime columns) The code is as follows: if (sourceFile.Name.EndsWith("x", StringComparison.InvariantCultureIgnoreCase

  • In our quest to handle some requirements to levelize the type of data users are adding to Sharepoint, we have come up with the idea that we need to add a choice field to all existing content types... will be required at first but could be turned off if needed. I was hoping that this could be done using a feature but a I am unable to determine what approach to take. Can the field be created programmatically and then somehow be added to all the content types or even the base content type. It seems that if you can add it to the 0x base content type it should work. Can this be done?

Data information