Anonymous
My feedback
9 results found
-
96 votesAnonymous
supported this idea
·
-
170 votes
Instead of “require password” security control, we intend to support “Require OTP” requirement for public links (via SMS, Email, or TOTP). I wanted to share where we are headed. We do not plan on delivering this ask as is, but we do intend to solve the security use case behind it.
Please comment if you disagree.
Anonymous
supported this idea
·
-
104 votes
Due to other higher priority items, this has been deprioritized.
An error occurred while saving the comment Anonymous
supported this idea
·
-
7 votes
Thank you for the suggestion! We do not plan to incorporate this change in our roadmap. We will let you know if anything changes.
Anonymous
supported this idea
·
-
19 votesAnonymous
supported this idea
·
-
42 votes
We are not planning releasing bulk delete functionality at this time since we are focusing our efforts on building faster and more usable users pages. We will revisit this feature request next year.
Anonymous
supported this idea
·
-
8 votesAnonymous
supported this idea
·
-
11 votesAnonymous
supported this idea
·
-
14 votesAnonymous
supported this idea
·
If someone is the owner of a folder, it would make sense to have an option to "Unshare" the folder, essentially removing all collaborators from the content. That or some sort of multiselect function to choose multiple at a time to either update access level or remove. To echo the 80+ other admins, it is a big pain point at the end of an engagement when we need to retain the content, but remove collaborators. Each time one account is removed, the entire page refreshes - if there are 20+ collaborators, this takes upwards of 10 minutes - it is a waste of time to need to perform such a tedious administrative task when it is so easily done on other platforms.