AdminTakatoshi Ueda
(Admin, Box)
My feedback
42 results found
-
8 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
33 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
9 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
34 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
11 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
18 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
30 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
23 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
20 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
8 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
AdminTakatoshi Ueda
(Admin, Box)
shared this idea
·
-
19 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
AdminTakatoshi Ueda
(Admin, Box)
shared this idea
·
-
11 votes
We have now released a feature allows users to block Hubs from being shared publicly via “anyone with the link”:
- Admins can set a global default in Hubs Global Presets to prevent open/public shared links for all new Hubs.
- Co‑owners can also restrict public shared links at the individual Hub level, as long as the admin hasn’t locked that setting.
But we haven't released a separate settings for Hubs links in general so I move this request back to "Under consideration". This is something we want to make in the future but not on our roadmap yet.
An error occurred while saving the comment AdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
2 votesAdminTakatoshi Ueda
(Admin, Box)
shared this idea
·
-
65 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
14 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
25 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
18 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
16 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
50 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
-
8 votesAdminTakatoshi Ueda
(Admin, Box)
supported this idea
·
My customer would like to restrict open/shared links to Hubs for security reasons. As a financial institution, they want to reduce the risk of external information leakage while making effective internal use of Hubs.
Even when a Hub is shared via an open link, we can use Box Shield classification labels to limit external users’ access to the underlying content. However, the callouts/speech bubbles and paragraph text authored on the Hub page can still be viewed. They want to avoid potential leakage if those callouts or paragraphs contain sensitive information.
For example, if Hubs offered a preset to restrict the scope of shared links (e.g., limit to users in the enterprise or invited users only), it would help mitigate this risk.