Hirotsuna Nakamura MKI
My feedback
15 results found
-
3 votesHirotsuna Nakamura MKI shared this idea ·
-
19 votesHirotsuna Nakamura MKI supported this idea ·
-
32 votesHirotsuna Nakamura MKI supported this idea ·
-
20 votesHirotsuna Nakamura MKI supported this idea ·
-
21 votesHirotsuna Nakamura MKI supported this idea ·
-
154 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.
Hirotsuna Nakamura MKI supported this idea · -
14 votesHirotsuna Nakamura MKI supported this idea ·
-
9 votesHirotsuna Nakamura MKI shared this idea ·
-
12 votesHirotsuna Nakamura MKI shared this idea ·
-
12 votesHirotsuna Nakamura MKI supported this idea ·Hirotsuna Nakamura MKI shared this idea ·
-
73 votes
We are creating a file request dashboard for Admins to manage their enterprise’s FR links.
Hirotsuna Nakamura MKI supported this idea · -
24 votes
Thank you for the suggestion. This is an interesting idea but not one we currently have on the roadmap. In the mean time, you can apply techniques such as caching (i.e. fetch what you need once for a session and keep it in local storage) to reduce round-trips, and the use the ?fields query string parameter to request only the minimal set of fields you need, which can reduce API response times.
Hirotsuna Nakamura MKI supported this idea · -
89 votes
A box-native metadata table is not currently on the roadmap, but we have launched our metadata query toolkit alongside a content-explorer element that can emulate the same experience.
Hirotsuna Nakamura MKI supported this idea · -
1 voteHirotsuna Nakamura MKI shared this idea ·
-
1 voteHirotsuna Nakamura MKI shared this idea ·