I have a client that would like to restrict their employees (users) from syncing the entire SharePoint files library. Instead, they'd like it so users can only sync certain files or folders. Ideally, AAD integration would be great so they can be like user X can sync Folders A, B and C but user Y can only sync B and D.
Anyone know if this is possible?
Per my test there is no feasible solution for your needs at this moment. For now, we just could limit files to sync at site level or library level, there is no way to limit at folder level per users.
Here is an official article for your reference: Limit sync for a SharePoint site (microsoft.com)
Related
I have 2 Sharepoint Sites, Site A only accessible by internal colleagues due to security concern, Site B can be accessed by external party.
I wish to synchronise Site A document library with Site B document library. Whenever there is update (addition/deletion/modification for PDF, jpeg, MS Word/Excel) of file within Site A document library, Site B document library will do the same automatically.
Hope masters here can share the experience or advise on feasibility. Thanks.
Maybe you can try this:
"Two-way sync", as its name suggests, is able to copy files in both
directions, keeping the two SharePoint Documents libraries in sync and
totally same with each other.
Besides, it provides the "Real Time Sync", which will execute
automatic sync as long as any changes are detected in the source cloud
if you choose "One-way Sync" at the same time. If you choose "Real
Time Sync"+"Two-way Sync". then the two SharePoint folders in two
accounts will be synced in time as long as either has any
modification. Also, 7 different sync methods are available for
different requirements.
https://www.multcloud.com/tutorials/synchronize-two-sharepoint-document-libraries-7201.html#:~:text=Files%20On%20Demand-,Step%201.,%22Sync%22%20in%20the%20toolbar.
I am trying to sync a sharepoint folder, "Testing" shown in the image below to my local device, but I have not been able to figure out how to do this.
I have looked at other sources and they said to find the "Sync" option, however I was unable to find this option. How should I go about doing this?
Edit: This is a shared folder that has been shared to me by another person in the organization, and can be accessed by multiple people
Had to read your post a few time but the answer is in the Edit section. The folder was shared to you by another user in the organization. This is most likely the reason why the sync option is not available. I'm a 365 admin in my organization and would make sure that users could not share SharePoint Doc Lib with other users and defiantly not be able to sync the library if the user could share a folder. This would be down to GDPR or Organization policy in place plus SharePoint Libraries will/should have user access in place. Being able to receive a share link from another user to me would mean that there is an issue with access to the SharePoint Document Libraries security/access settings.
If you return to classic SharePoint, you would see the "Sync" option.
To sync sharepoint folder to local device, you have to allow items from this document library to be downloaded to offline clients. Please go to library settings-> Advanced settings, make sure you select yes.
I want to distribute info on sharepoint to differenct groups A,B, and C and I want only the content for group A to be seen by group A, only the content for gorup B to be seen by gorup B, and only the content for gorup c to be seen by gorup C.
What is the best way to structure a Sharepoint team site?
Currently I have
team/sites/groupA
team/sites/groupB
team/sites/groupC
and I was going to set up 3 sharepoint groups for A,B and C and permission the three sites to the 3 sharepoint groups.
But can/should it be set up with only 1 site like:
team/sites/MainSite
and then all the permissions managed using inherited permissions etc...
I am a sharepoint beginner and don't know much about the inheritied permissions or heirarchy of how a single site would work. Any thougths on which way is better? I would like to make the site or sites as easy to maintain as possible.
Thank you!
The way you have desgined it as site collection is best approach. the best approach is if you need fine grained permission for a site create a site collection.
Although regarding your other question of having main site and then having sub-site it would not be possible using inheriting permission, you would have to use fine grained permission if you want to give diffrent permission for each subsite.
if the gr
although you could have done it by stop inheriting permission but it should be only done when you know the groups a ,b & c would be having small number of users
I have a requirement in a Sharepoint 2013 setup wherein I've to give access to external users to a document library. Each User will have a folder by their name, and would be allowed to ACCESS their folder ONLY. They are not even allowed to see each other folder names. They can anytime upload additional or delete the existing documents. External Users are setup using FBA.
Inside the network, there is a Windows user who'll have access to all the folders and documents of that library. I don;t think standard document library can handle this since there is no "Deny View" Permission in Sharepoint.
Sharepoint Folks - Please guide what will be the best way to handle this kind of requirement.
I don't think having a bunch of folders makes sense. However, you could have users upload documents to the shared documents library and have a column in the documents library of the user's username. You could then create a content query on that list to query documents that the current user uploaded. You could then replicate a "folder" type of feel by creating this page, styling it, and directing all users to it.
Let me know what you think of that.
There actually is a way to deny all users. Remove the Authenticated Users, and Remove Anonymous Access from the Library. I agree, that using folders is the wrong idea here. Folders can cause much more harm than help in certain situations.
Create a site to hold multiple libraries, or disinherit the site, remove everyone not essential to the libraries, and use it as a container for the document libraries. Each library can still have it's own unique permissions, and without Authenticated or Anonymous, you'r essentially telling SharePoint that none has access except for the users specified in the ACL's on that library.
You COULD leave the permissions intact on the site and powershell the creation of the document libraries within the site, assigning custom permissions.
To quickly summarise my question:
Is it feasible to programmatically change the name of a directory (with both files and sub-folders) in SharePoint? I am expecting that users will have files checked out on at least some occasions what I am attempting the rename.
The background:
I am currently contracting for a company that produces web based software (ASP.NET) with a configurable document management system. The system can be configured to use different underlying systems, with the most common environment being SharePoint (WSS 3).
I have been assigned a task to extend what has to now been a fairly simple system (simply output files into a fixed directory structure, occasionally read). Having never worked with SharePoint before I am doing some research on best practices, and am attempting to work out what is viable. At this stage I do not have access to a testing environment myself, so am limited to reading up online.
One request is to have the directory structure reflect the name (as one example) of the current client - so all documentation for a client will be in one place, and can be accessed externally via SharePoint or other compatible applications. The specification cites that if the name of the client changes then the directory structure should immediately update. My concern is that this will either directly cause errors (eg. Permission denied) or indirectly cause errors (loss of work for users who have externally checked out files).
As a follow up question if there are concerns with the above, is there a better way to implement the above? I have looked at suggesting the users use views to access the structure in SharePoint, however there is a concern from our BA that users will not be able to directly upload new files into this structure.
Thanks
The issue with Folders in SharePoint is that they are not really folders in the way you would expect of a file system. All files in a SiteCollection are stored in one big-assed table on the Database (checkout the AllDocs table).
I cannot categorically say it is safe to rename the folder without doing a bit of testing, I know that the folders "name" is not the key to accessing the document, despite it appearing to be based on the Url you see in the browser.
The best bet is to do a quick test, but I am pretty sure that your plan will not be a problem.
The potential issue is if any Content Query Web Parts etc rely on specific folders to exist or if any other "code" or "pages" look for that folder and not the folderId.
Save the content of the list before you "attempt" it in production. You don't want to loose data.
Checked out documents will still work the way you expect them to.
You may however have to run a crawl again.