Help shape the future of Box

Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!

See user guide here.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Localize the name of "Classification" metadata template to user's language

    User cannot name of "Classification" metadata template which is automatically created when the user create Classification policy. At least it should localize to Box admin's language (ex "分類" in Japanese)

    1 vote
    Sign in Sign in with Box
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Shield  ·  Flag idea as inappropriate…  ·  Admin →
  2. Be able to write definition in multiple language (ex.ENG/JP) on "classification" definition field.

    Function request regarding the Definition field of "Classification"
    Would like to enter a description with each language in the "Classification Definition" column.
    Even if English / Japanese can be written together in the current definition column, currently, each lines breaks are not possible. hope to make it possible.

    However, it is in trouble because a line break cannot be made each.

    1 vote
    Sign in Sign in with Box
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Shield  ·  Flag idea as inappropriate…  ·  Admin →
  3. Classification definition

    Currently when classifying a document it is only possible to see the top 2-3 lines and is not rich text therefore doesn't support returns, bold type, links, bulleted lists or colour.
    While the full 300 characters are displayed in the details pane, Users need to see all the details prior to applying the classification.

    REQUEST: To make the dropdown either expandable (i.e. 'show more') or to show the full 300 character classification definition and to make the definition field 'Rich Text' so its possible to give more context to the classification e.g. provide a list of example documents or link…

    1 vote
    Sign in Sign in with Box
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Shield  ·  Flag idea as inappropriate…  ·  Admin →
  4. Request File Marked Malicious Error in Box Web App UI and api

    Constant monitoring the "enterprise events adminlogs" for FILEMARKEDMALICIOUS events is not feasible for our application. Request is to add filemarkedmalicious error, similar to filesizelimitexceeded error, so that the user the can be instantly notified of potential problem at file upload time for best user experience.

    Instant notification is available today in our application, without this ability our users would see a degradation in their app experience.

    1 vote
    Sign in Sign in with Box
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Shield  ·  Flag idea as inappropriate…  ·  Admin →
  5. 3 votes
    Sign in Sign in with Box
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under consideration  ·  0 comments  ·  Shield  ·  Flag idea as inappropriate…  ·  Admin →
  6. Events API - Add Policy Name to CONTENT_WORKFLOW_UPLOAD_POLICY_VIOLATION

    Currently, when an Upload Policy violation occurs, Box reports on that violation in 3 ways:
    1. Email notification
    2. Admin Console -> Reports tab
    3. Events API

    In the email notification and admin console->reports, Box provides the policy name for which the violation is occurring. However, Box does NOT include the policy name in the Events API entry, which causes a problem when we are pulling logs (via the Events API) into external reporting/SIEM tools like ArcSight/Splunk.

    Request: Add 'Policy Name' to the CONTENTWORKFLOWUPLOADPOLICYVIOLATION entry in the Events API (to reach parity with the native Admin…

    1 vote
    Sign in Sign in with Box
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under consideration  ·  1 comment  ·  Shield  ·  Flag idea as inappropriate…  ·  Admin →
  7. Expose in the API the ability to restrict collaboration in a folder within the company only

    This would allow to disallow inviting external users based on folder metadata such as classification

    0 votes
    Sign in Sign in with Box
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Shield  ·  Flag idea as inappropriate…  ·  Admin →
  8. 2 votes
    Sign in Sign in with Box
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Shield  ·  Flag idea as inappropriate…  ·  Admin →
1 3 Next →
  • Don't see your idea?

Feedback and Knowledge Base