Skip to content

Carrot

My feedback

3 results found

  1. 1,315 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Carrot supported this idea  · 
  2. 335 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Carrot supported this idea  · 
  3. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Carrot commented  · 

    An "anyone with existing access" link sharing option is a basic feature of mainstream filesharing platforms like Google Drive or Microsoft Onedrive. There is no reason why it shouldn't be implemented here as well. Access request spam would be no different than on those platforms.

    For anyone reading this who doesn't understand the use case, take this as an example:
    Say I write up a new document that needs to be reviewed and approved by the group of people I share a folder with - all of them have Proton accounts and edit access to the folder just like I do.

    Today, there is no way for me to tell those people "Hey everyone, new doc is posted. Please review and provide your comments <LINK>" without creating a unique, *public* editor link for that document. A link which, mind you, will then work for ANYONE who has it, not just the people on the list who already have permission to access it. Yes, that link can be password-protected, but now you're making people who already have access to the file enter a password to access it. Which is extremely clunky and annoying.

    If you still insist on using the public link workaround, it still promotes the proliferation of a bunch of anonymous editor links to files and subfolders. With no way to track how many editor links exist in a centralized way, that presents a severe opsec/hygiene risk.

    This is a no-brainer, y'all.

    Carrot supported this idea  ·