Anonymous
My feedback
39 results found
-
79 votes
We are currently researching the requirements for this feature and validating our technical architecture.
Anonymous supported this idea ·
-
24 votes
Anonymous supported this idea ·
-
391 votes
We understand the request, but unfortunately this is not on the near-term roadmap.
Anonymous supported this idea ·
-
19 votes
Anonymous supported this idea ·
-
71 votes
Anonymous supported this idea ·
-
7 votes
Anonymous supported this idea ·
-
65 votes
This is still on the roadmap.
Anonymous supported this idea ·
-
145 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 ·
-
14 votes
Anonymous supported this idea ·
-
11 votes
Anonymous supported this idea ·
-
20 votes
While we recognize the importance of this feature, it is not something we plan to introduce in the near term. We will certainly keep this in mind for future roadmap inclusion and we will keep the status of this request updated to accurately reflect our current position.
Anonymous supported this idea ·
-
30 votes
Anonymous supported this idea ·
-
388 votes
Anonymous supported this idea ·
-
1 vote
Anonymous shared this idea ·
-
28 votes
This is currently not planned but we will re-evaluate priorities in Q3/Q4 of FY23
Anonymous supported this idea ·
-
20 votes
Anonymous supported this idea ·
-
14 votes
Anonymous supported this idea ·
-
6 votes
An error occurred while saving the comment Anonymous supported this idea ·
-
114 votes
Anonymous supported this idea ·
Additional use case would be to notify an uploader that a piece of content has been approved by an organization. Marketing use case using an external agency receives an email stating the internal team has approved the content.