Shared link asks viewers to request access. Why does this happen?

I’ll see what I can do, Hannah.  I think most of them have already requested access and viewed this file, but the next time someone asks for approval, I will post here.

Many thanks again!

Not a problem, skepticalthinker!

The thread will remain open, so whenever you can, just get back to us with any updates.

Thanks again and have a great weekend!

Hello again, Hannah.

I was finally able to get the screenshot you suggested might be helpful here.  It is included below along with some others that illustrate the issue I'm having.

First, as I showed in my initial post, these are the settings for the file in question:

It's set to allow access to anyone with the link, and downloads are disabled.

I've shared the link (via email, not via Dropbox's "Share Link" option) with a number of people.  When they click on the link, they receive this notice:

(The person who shared this screenshot with me has a Dropbox account, but I'm not sure if or how many others I've shared the link with do—if that matters.)

I have shared many files in this way—as recently as about a month prior to this one—and recipients never had to do anything beyond clicking the link to be taken directly to the shared file.

When I click on the link to determine "Who Has Access" to the file in question, it lists me, plus the people who have so far requested access.  Each is listed as "Can View," but when I view that drop down menu, it notes that these people can download the file despite my disabling that ability as pictured above:

Furthermore, from this same screen, when I move from "People" to "Links," it says that "Anyone with this link can view" (which hasn't been the case):

I hope this might help to determine why recipients must request access even though I have the file set to be viewable to anyone with the link.

Thanks again for your interest in my issue.

Hi @JasonSilverDBX ,

Hopping in here to add some extra info we've uncovered as it looks like there was a recent update to how "Can View" links are generated.

When you send someone a "Can View" link, it now has a special "rlkey=" field. There may have been a similar access code in previous links that stayed in the URL as you navigated, but the issue we're running into now is that when you navigate into any of the folder structure of a "Can View" link, the rlkey disappears from the URL in the browser address bar, leaving access tied to the browser session, so if you were to copy the updated URL and open it in a new session or send it to someone else or open pages from your browser history expecting it to work, now you get either a "Sign Up" page or a "Request Access" page. This was NOT an issue with previous "Can View" links before this update.

We send out links to partners and agencies that then want to share specific links to specific folders in our links amongst their teams, but this update breaks that functionality and will cause confusion as we get kickbacks like, "our team is having trouble with that link", "we tried to request access", "it's making us create a Dropbox account and we would prefer not to do that".

We actually had a similar wave of these issues when shares suddenly defaulted to "Can Edit" invite links on our Dropbox a year or so ago, and manually switching to "Can View" for each share was the solution that made sharing viable, but this update brings back most of the issues we had with "Can Edit" links.

Regarding the issue described in my OP, and on the recommendation of JasonSilverDBX, I contacted Dropbox Support and found an answer to my question.  Apparently, since the recent Dropbox update (with the new "rlkey" share links), when you share a file that has restrictions (e.g. downloading disabled) via a link, and the recipient is logged into Dropbox, that recipient does not have access until the person sharing the file approves it.  Once the access is approved and the recipient adds it to their Dropbox, that recipient has full access to the file and any restrictions placed on that file are gone.  This technically solved my problem, in that if I don't want recipients to have the ability to download shared files, I can inform them to log out of Dropbox before viewing the files (in which case they would view it in their browser as opposed to from their own Dropbox).  However, I think this recent update that caused this issue has introduced unnecessary confusion and makes one of the helpful features of Dropbox Essentials more complicated.

This is not a great response. If you are a indeed a product manager then you should already have access to see the necessary details with this customer.

Sending them to contact support (which is a lower level than product manager, I guess) is just "passing the buck".

I have the same problem as this person: 
I have a shared file set to be viewable by anyone with the link, and I've sent the link to those I want to view the file (see screenshot). However, when they access the link, Dropbox states they "do not have access to this file" and offers the option to request access, which I must individually approve. I have other files configured with these same settings, and those with whom I've shared those links can access them without any separate approval. I don't know why this particular file is different. Am I missing something?

How do I give continuous access to share and see and download and edit a FOLDER to my team?

Hello mkeller 

I was the OP on this thread, and I found a workaround for this issue.  I suggest reading through the thread, especially page 3.  See if that addresses your issue as it did mine.