Skip to content

Anonymous

My feedback

1 result found

  1. 2 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
    Anonymous commented  · 

    Problem / Why it matters:
    • Customers using Hubs as client/extranet portals need client-specific Terms of Service at the Hub level (not enterprise-wide).
    • Many firms run multiple client portals, each with different legal terms, and they must be able to prove who accepted, when, and under what terms before granting access.

    Requested capability:
    • Add a Hub/Portal-specific ToS “splash page” that requires users to Accept / Decline before viewing Hub content, with mandatory authentication and an audit trail.

    Current State:
    • This do this with HighQ Client Portals.
    • But they’re pushing to replace HighQ Portals with Box Hubs.

    An error occurred while saving the comment
    Anonymous commented  · 

    PROBLEM / WHY IT MATTERS
    • Customers using Hubs as client / extranet portals need client-specific Terms of Service at the Hub level (not enterprise-wide).

    • Many firms run multiple client portals, each with different legal terms, and they must be able to prove who accepted, when, and under what terms before granting access.

    REQUESTED CAPABILITY
    • Add a Hub/Portal-specific ToS “splash page” that requires users to Accept / Decline before viewing Hub content, with mandatory authentication and an audit trail.

    Anonymous supported this idea  ·