I need to share some folders from a SharePoint site to a user outside my organization. When i choose the folder and click share to specific people, i get an error
I did some searching and there is an official documentation from Microsoft that recommends checking the sharing permissions etc. All steps suggested are OK but i still can't share the folder. FYI the folders is a pretty large one and the whole library has 710.000 files and folders and 990GB of storage. I mean, it is utterly annoying the way it works. If i can't share a large folder why do i even get the option to do so? Is there any workaround besides distributing the files and folders into many libraries which will be chaotic?
PS. I did the same question on sharepoint.stackexchange.com but no answer in a week. Please i need help
Related
I am trying to reorganize the microsoft sharepoint of my team, into thematic folders, but I'd like to keep the links to the original files after moving them. Do you know if it's possible?
Thank you!
Do you mean file sharing link? If true, please check this article:
When you move the files within site (inside of a library or between libraries on the same site), all the previously shared links to those files will still keep working!
When you move the files to a totally different site,remember to check the Keep sharing with the same people box:
In this way, the previously shared link will still work for the recipient.
Limitations
The ability to keep sharing links is only available for files, not
folders
When a shared folder is moved to another site, the link will stop
working. The recipient will receive This link has been removed
message.
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 have a feeling this is a long shot, but is there a Google script that can transfer everything in a Google site to SharePoint or a Google drive folder to SharePoint?
I would rather just use Google drive for collaboration as it is 100 times better than SharePoint (IMHO), but my company insists on using SharePoint. That being said, our team would like to continue using our Google site for collaboration and documentation which is why I am wondering if there is a script of some sort to transfer documents from Google to SharePoint?
Well, this isn't an exact answer to my question. But this ended up making the process about 99% easier. I installed google drive locally so all of my files are placed in the google drive folder. I then opened sharepoint, and switched to explorer view. I then simply copied/pasted all the folders from google drive to the sharepoint folder, and about 30 seconds later all files were synchronized. It would be pretty simple to write a script to copy the files/folders from the google drive folder to the sharepoint folder. This was a simple way to solve an annoying problem, I hope this is helpful.
I need to work with several teams and need to be able to share requirements and design documents. Most people won't be too technical, so I want to avoid source code tools. The main requirements are:
Easy sharing via links. I don't want people to have to install multple tools just to see a file or learn anything about svn checkout.
Permissions - I want to allow view only access to most people, with some having add/edit permissions. I don't want anyone to be able to permanently delete anything.
Revision History - I want to see who has added and edited files and be able to revert to previous versions.
I've tried Dropbox and SkyDrive, but they each have faults. Dropbox allows users to permanently delete files, and it will even delete the file from your local machine when it is synced. SkyDrive doesn't allow enough fine grained permissions or revision history. Do I need a CMS system like Drupal]? Would Sharepoint be the proper tool? I don't necessarily need an open source solution. The easier it is to set up and administer, the better.
Just my personal bias, but I hate Sharepoint. (I see this Q is tagged Sharepoint)
I much prefer some sort of Wiki, and have had good experience with TWIKI. It certainly meets the three basic requirements.
AFAIK Dropbox never deletes files "permanently" but you can undo it via the web interface. If I remember correctly you also can restore old versions of files but I cannot try it right now.
Adobe Buzzword might do most of what you are looking for.
If you do not need online document creation, a traditional CMS is not really what you are after. Drupal could serve your purposes, but it would not be straightforward- afterall, file attachments are second class citizens for a web content system.
Alfresco is a system I've heard used as a competitor for Sharepoint and useful for managing documents.
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.