Best practice for setting up a library with restricted access for different user

%3CLINGO-SUB%20id%3D%22lingo-sub-1233644%22%20slang%3D%22en-US%22%3EBest%20practice%20for%20setting%20up%20a%20library%20with%20restricted%20access%20for%20different%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1233644%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20long%20list%20of%20spec%20and%20technical%20documents%20that%20i%20want%20to%20share%20with%20external%20customers.%3C%2FP%3E%3CP%3EBut%20i%20only%20want%20certain%20customers%20to%20view%20certain%20documents.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3Ethere%20are%20approx%204000%20documents%20covering%20approx%20300%20products%3C%2FLI%3E%3CLI%3Ethere%20are%20approx%20300%20customers%20who%20need%20access%20to%20information%20on%20between%202%20and%2050%20products%3C%2FLI%3E%3C%2FUL%3E%3CP%3EFor%20example%2C%20if%20i%20assume%202%20customer%20and%207%20docs.%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3ECustomer%201%20needs%20to%20be%20able%20to%20view%20doc%201%2C3%2C5%2C7%3C%2FLI%3E%3CLI%3ECustomer%202%20needs%20to%20be%20able%20to%20see%20doc%201%2C2%2C7%3C%2FLI%3E%3C%2FUL%3E%3CP%3EI%20can%20add%20extra%20columns%20to%20identify%20the%20customer%20and%20product%20type%20and%20can%20views%2C%20but%20i%20am%20not%20sure%20I%20would%20restrict%20the%20permissions%20or%20whether%20this%20is%20the%20best%20way%20to%20achieve%20this.%20One%20customer%20may%20have%26nbsp%3B%203%20or%204%20members%20of%20staff%20that%20need%20to%20access%20the%20spec%2C%20so%20the%20easiest%20way%20of%20allowing%20access%20is%20via%20domain%20level%20rather%20than%20continually%20adding%20and%20removing%20individuals%20within%20a%20organisation.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20do%20however%20have%20some%20questions%3C%2FP%3E%3COL%3E%3CLI%3EIs%20this%20the%20best%20way%20of%20achieving%20this%20and%20if%20so%20how%20can%20i%20restrict%20access%20to%20only%20the%20created%20view%20rather%20than%20the%20whole%20library%3F%26nbsp%3B%26nbsp%3BIs%20it%20possible%20to%20share%20a%20view%20so%20that%20it%20appears%20in%20a%20%22window%22%20of%20its%20own%20but%20will%20not%20allow%20the%20filter%20to%20be%20accessed%20to%20full%20all%20the%20other%20records%3C%2FLI%3E%3CLI%3Ewould%20I%20be%20better%20creating%20private%20channels%20in%20teams%20and%20adding%20the%20view%20as%20an%20app%2C%20I%20have%20tried%20this%20and%20it%20does%20work%2C%20but%20I%20don't%20think%20i%20can%20give%20access%20to%20individuals%20at%20domain%20level%2C%20but%20would%20need%20to%20add%20all%20individuals%20with%20their%20full%20email%20address%20and%20continue%20to%20maintain%20this%3C%2FLI%3E%3CLI%3EIs%20there%20a%20better%20way%20of%20achieving%20this%2C%20so%20keeping%20other%20documents%20secure%3F%3C%2FLI%3E%3C%2FOL%3E%3CP%3EMany%20thanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1233644%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPermissions%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Contributor

I have a long list of spec and technical documents that i want to share with external customers.

But i only want certain customers to view certain documents.  

  • there are approx 4000 documents covering approx 300 products
  • there are approx 300 customers who need access to information on between 2 and 50 products

For example, if i assume 2 customer and 7 docs. 

  • Customer 1 needs to be able to view doc 1,3,5,7
  • Customer 2 needs to be able to see doc 1,2,7

I can add extra columns to identify the customer and product type and can views, but i am not sure I would restrict the permissions or whether this is the best way to achieve this. One customer may have  3 or 4 members of staff that need to access the spec, so the easiest way of allowing access is via domain level rather than continually adding and removing individuals within a organisation.  

 

I do however have some questions

  1. Is this the best way of achieving this and if so how can i restrict access to only the created view rather than the whole library?  Is it possible to share a view so that it appears in a "window" of its own but will not allow the filter to be accessed to full all the other records
  2. would I be better creating private channels in teams and adding the view as an app, I have tried this and it does work, but I don't think i can give access to individuals at domain level, but would need to add all individuals with their full email address and continue to maintain this
  3. Is there a better way of achieving this, so keeping other documents secure?

Many thanks

 

 

 

0 Replies