132 results found

1. Stop or modify instant suspension of new user email addresses on account setup, or give admins access to your blocklist

   When a new user account is set up, a confirmation email is automatically sent to the login address for the account. Currently, if this message is bounced, the user's email address is immediately placed on your block list.

   So - I create a new staff email account in 365, then use that email address to set up a Box account. Box immediately sends a confirmation email message - but 365 is having a slow day and the gateway hasn't yet caught up with accepting messages for that address. The confirmation message is bounced, and the user's email address is immediately placed on your block list.

   The problem is that I (as the Box and 365 admin) have no way of knowing this. Box does not inform me that it has happened - it simply offers me the option to resend the confirmation email, and does not tell me that this option can never work because the address is being blocked behind the scenes. So I waste many hours trying to trace the messages in 365, and to find out why they haven't arrived. I resend from Box several times, with the same result.

   This is stupid, in three different ways:
   1: When sending email messages of any kind, all sensible systems wait and retry at least once before deciding that the message has failed. Why doesn't Box do this before placing an address on a hidden blocklist?

   2: As admin/co-admin I really need to know when one of my user account login addresses is being blocked by Box - but I have no way of finding this out.

   3: As the Box account creator, I really need to know when the confirmation email message has bounced back, because it means that the account creation has failed and the user will not be able obtain a password, even if I try (apparently successfully) to resend the confirmation. Your system does not notify me when it blocks an account signup email address.

   Please implement at least one of the following:

   A: When a confirmation message for a new account is bounced, send a notification to the admin/co-admin who tried to create the account that this has happened, and how to resolve it.

   B: When an email address is being blocked, it makes no sense to present admins/co-admins with a link to send any kind of message to it. Please stop doing this.

   C: When a new account confirmation email is bounced, please wait 15 minutes and retry before blocking the address.

   D: Give admins/co-admins access to the list of emails in their domains which are on your blocklist - even if this access is read-only. At least then they can see what the problem is, and contact support to have an address removed.

   When a new user account is set up, a confirmation email is automatically sent to the login address for the account. Currently, if this message is bounced, the user's email address is immediately placed on your block list.

   So - I create a new staff email account in 365, then use that email address to set up a Box account. Box immediately sends a confirmation email message - but 365 is having a slow day and the gateway hasn't yet caught up with accepting messages for that address. The confirmation message is bounced, and the user's email address is immediately… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Need Permission level between Viewer/Uploader and Editor

   Viewer/Uploader is good, but, not good enough for all use cases; and Editor is too much--especially for external collaborators.

   External collaborators need to be able to fix problems they accidentally create (e.g. uploading the wrong file) or wanting to change the name of a folder when they realize that the current name may be confusing (who hasn't done that?).

   I agree with others' comments that there needs to be a permissions level between Viewer/Uploader and Editor. I can see at least four possible solutions:

   1) Allow collaborators to rename a folder/file. This could help with the accidental upload as well since they could add some text to the file/folder name to reflect that it needs to be discarded (e.g., _DISCARD) to make it obvious for clean up later. This adds more maintenance on the editor, but, would be better than nothing.

   2) Allow the ability to 'Move' (not delete) a file/folder (say, into an Archived or Discarded folder where external collaborators can move folders/files they created in error.

   3) Allow them to mark something as 'discard' (maybe a toggle) that automatically sorts them to the top or bottom for maintenance; or, could automatically put these files/folders into a secondary folder, called DISCARDED (similar to DELETE, but, the editor would have to actually delete them from the DISCARDED folder (or they can auto delete at some timeframe). At least they'd be out of the way and the editor can easily look in there to see what is there. It would prevent accidental deletions as external collaborators should be able to recover items from the DISCARDED folder.

   4) Give the admins the ability to create a customized role where they can add capabilities beginning with some permission level. For example, I can start with Viewer/Uploader and create Viewer/Uploader Plus, which has all the Viewer/Uploader permissions PLUS what you want to add, in my case, Move and/or Rename files/folders.

   Basically, Viewer/Uploader is good, but, not enough for all use cases. And, Editor is WAY too much--especially for external collaborators.

   Thank you for considering!

   Viewer/Uploader is good, but, not good enough for all use cases; and Editor is too much--especially for external collaborators.

   External collaborators need to be able to fix problems they accidentally create (e.g. uploading the wrong file) or wanting to change the name of a folder when they realize that the current name may be confusing (who hasn't done that?).

   I agree with others' comments that there needs to be a permissions level between Viewer/Uploader and Editor. I can see at least four possible solutions:

   1) Allow collaborators to rename a folder/file. This could help with the accidental upload as well… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Prevent paid accounts from inviting free accounts with the same corporate e-mail domain

   It'd be good If managed users can't invited free accounts who has the same e-mail domain or notify Admin immediately so Box users can comply with fair use policy.

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Users and Groups  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Invite an external guest who has an email domain connected to a box enterprise account, but is not licensed.

   Invite an external guest who has an email domain connected to a box enterprise account, but is not licensed.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Ability to exclude certain email addresses from accessing public links.

   Some links are shared with individuals both in and out of the organization. When the individuals move on, they no longer need access to our folders. It would be great if we could exclude their email addresses from future access.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Copy or Duplicate existing groups

   Would appreciate the ability to create copies of existing Groups, mainly for its members - not so much the permissions given to that group.

   My use case: We've got an "ALL" group that has access to numerous folders. There is one user that does not want access to one of those folders. So I'd like to be able to copy the "ALL" group and remove that user, rather than re-create our "ALL" group which has a lot of members.

   There also is no good way to bulk add members to a group. Typing each person is cumbersome, it'd also be nice to have a check list of the user directory so I can select which ones I want to act upon.

   Would appreciate the ability to create copies of existing Groups, mainly for its members - not so much the permissions given to that group.

   My use case: We've got an "ALL" group that has access to numerous folders. There is one user that does not want access to one of those folders. So I'd like to be able to copy the "ALL" group and remove that user, rather than re-create our "ALL" group which has a lot of members.

   There also is no good way to bulk add members to a group. Typing each person is cumbersome, it'd also be… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Tenant Admin and Co-Admin can check group members from the collaborator list

   If the group permission setting is set to "Admins only", only the user who is the gouroup admin can display the members of the group from the collaborator list of the invited folder.

   Tenant admin and co-admin cannot be set as group admin.
   Even if you are a member of a group or have been invited to the same folder, you will not be able to see the members of the group without navigating to the admin console.

   We request functional improvements so that tenant admin and co-admin can easily check from the collaborator list.

   (日本語)
   テナントの管理者・共同管理者がコラボレータ一覧からグループのメンバーを確認できる。
   グループの権限設定を「管理者のみ」にしている場合、招待されているフォルダのコラボレータ一覧からグループのメンバーを表示させることができるのは、グループの管理者となっているユーザーのみです。

   テナントの管理者や共同管理者は、グループの管理者に設定することができないため、グループのメンバーに含まれていたり、同じフォルダに招待されていても、管理コンソールに移動しないとグループのメンバーを確認することができません。

   テナントの管理者・共同管理者がコラボレータ一覧から簡単に確認できるように改善を要望します。

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Ability to customize collaborator privilege

   Want to automate the task of "when the viewer / uploader notices the need to update a particular locked file, ask the editor to confirm and approve the file update"?
   To do this, from the perspective of user permissions, you need collaborator permissions that remove one permission from the viewer / uploader and grant one permission.

   -Collaborator authority that grants manual workflow startup authority to viewer / uploader authority and cannot unlock files.

   By realizing this authority, the following workflow can be automated in combination with Box Relay.

   (1) Lock the approved document managed by the editor.
   (2) The viewer / uploader notices the need to update the file.
   (3) The viewer / uploader starts a manual workflow for the file.
   (4) The information is notified to the editor by Box Relay, and the editor confirms the content and approves the work.
   (5) The file lock is released by Box Relay.
   Box Relay assigns a task to the viewer / uploader that invokes the manual workflow.
   (6) After the work is completed, the viewer / uploader presses the task completion button to proceed with the workflow.
   (7) The editor confirms the contents and approves the file.
   (8) Approved files are locked again by Box relay.

   The above is a specific story, but in general there are only 7 collaborator privileges, so many BOX users may have tasks that they want to perform but cannot. There is a possibility that all can be solved by creating a customizable collaborator privilege that allows each item to be set freely.

   Want to automate the task of "when the viewer / uploader notices the need to update a particular locked file, ask the editor to confirm and approve the file update"?
   To do this, from the perspective of user permissions, you need collaborator permissions that remove one permission from the viewer / uploader and grant one permission.

   -Collaborator authority that grants manual workflow startup authority to viewer / uploader authority and cannot unlock files.

   By realizing this authority, the following workflow can be automated in combination with Box Relay.

   (1) Lock the approved document managed by the editor.
   (2) The viewer… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Augment existing collaborator permissions in inherited subfolders

   Scenario:

   Folder A is shared with User X with Viewer permission
   Folder B is a subfolder of Folder A, on which User X requires Editor permission

   According to support, the only way to accomplish this in the web UI is to first remove User X as a collaborator on Folder A, add them as an Editor on Folder B, and then re-add them as a Viewer on Folder A

   This is clunky, annoying, and results in a lot of extra notifications.

   Clearly this is supported by the underlying file system because you can do it directly with the Box CLI:

   box collaborations:create <folder ID> folder --role editor --group-id <group ID> --no-notify --as-user <user ID>

   This results in the correct assignment. However while trying to do this in the web UI, an inheritance warning prompt appears and will change the collaborators permission at the parent level too, which is not desired.

   This seems to be a very common use case and I'm shocked at the app behaving this way. Please fix this! We need to be able to augment inherited permission on subfolders from the web UI.

   Scenario:

   Folder A is shared with User X with Viewer permission
   Folder B is a subfolder of Folder A, on which User X requires Editor permission

   According to support, the only way to accomplish this in the web UI is to first remove User X as a collaborator on Folder A, add them as an Editor on Folder B, and then re-add them as a Viewer on Folder A

   This is clunky, annoying, and results in a lot of extra notifications.

   Clearly this is supported by the underlying file system because you can do it directly with the Box CLI:

   … more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Users and Groups  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. I would like to have a collaboration role that only allows me to reference shared links.

    I would like to have a collaboration role that only allows me to reference shared links.
    Alternatives (1) through (3) could not be adopted for a reason.

    (1) Why not just use the Previewer?
    I want to collaborate from the top of the folder tree to prevent confusion about where I collaborated.
    For this purpose, I want a collaboration role that can only refer to shared links that cannot refer to other files.

    (2) Why don't we just create a shared link that is open to everyone and add a password?
    If you make it public, you won't know who has accessed it.
    Even with a password, there is a possibility of leaks.
    If you are a collaborator, you can restrict the disclosure to collaborators only, so it is secure.

    (3) Why don't you invite only the files you want to show?
    I want to collaborate from the top of the folder tree to prevent confusion about where I collaborated, so I can't do that.

    I would like to have a collaboration role that only allows me to reference shared links.
    Alternatives (1) through (3) could not be adopted for a reason.

    (1) Why not just use the Previewer?
    I want to collaborate from the top of the folder tree to prevent confusion about where I collaborated.
    For this purpose, I want a collaboration role that can only refer to shared links that cannot refer to other files.

    (2) Why don't we just create a shared link that is open to everyone and add a password?
    If you make it public, you won't know who… more

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Adding Company Information to Users to Prevent Wrong User Invitations

    When I invite a user with Box, information other than the email address is not displayed, so I think it is possible to invite another user by mistake.

    In order to solve this problem, I think it is necessary to display not only the email address and name but also the company information that the user belongs to when inviting the user.

    For managed users, we want to make it possible to register company affiliation information in account settings and so on, so that it can be displayed when inviting collaborators.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Private folder within a shared folder

    I want to be able to create a private folder for myself within a shared folder where I am the owner and many others are editors/viewers.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. shared links need to remain the same if file is revised

    We create PDFs from InDesign files, which I then right click the PDF and "Copy Shared Link" to send to our coworkers and place in a shared file. If we make changes to the InDesign file and resave the PDF with same name and address, the links should remain the same. Right now if we revise the PDF the links are broken and we have to resend new links to everyone and place in the shared files. (We used to use Egynte, and if we made changes to a PDF like this (same name, address) the links would still work - this is a tremendous time saver.)

    We create PDFs from InDesign files, which I then right click the PDF and "Copy Shared Link" to send to our coworkers and place in a shared file. If we make changes to the InDesign file and resave the PDF with same name and address, the links should remain the same. Right now if we revise the PDF the links are broken and we have to resend new links to everyone and place in the shared files. (We used to use Egynte, and if we made changes to a PDF like this (same name, address) the links would still work… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Verify account existence before triggering password reset email

    When I tried to log in and couldn't, I requested to reset my password and received the following message:
    We've sent you an email to reset your password
    You will receive an email from us in the next few minutes. Click on the link in the email to change your password.

    After not receiving an email, I tried registering for a new account. It turns out I apparently never had an account.

    Before telling users that you are sending a password reset email, maybe CHECK to see if they actually have an account so you can provide useful information?

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Users and Groups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Collaboration expiration for specific collaborators

    Collaboration expiration can only be applied on a folder level at the moment and cannot be applied to specific collaborators. I would like this feature for specific collaborators in a folder.

    18 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Hide user in autocomplete

    Similar to how you can hide users from the GAL in Exchange, I would like the ability to hide certain accounts from the auto complete when adding as a collaborator. You would still be able to invite the user by entering in the full email address.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Co-admin should be able to login to other co-admin accounts and service accounts

    Box co-admin should have the ability to log into other co-admin accounts and application services accounts to manage content. Today, you rely on using Box APIs or the primary Box admin account. It would be more convenient for coadmins to use the Box webapp instead.

    14 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Control managed user external collaboration to webmail accounts

    Setting that allows admin of corporate instance to control/limit managed users being collaborated into personal Box webmail accounts. This would be a setting to control/limit an outside Box webmail user collaborating a corporate managed user into its personal account.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Users and Groups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Collaborator Restriction to a folder.

    We need the ability to decide which subfolders a specific collaborator can access. Specifically, we need to restrict access of one collaborator to a subfolder (and all of its contents/subfolders). I was told this is not something Box cannot do. This is an issue. We need to set up an ethical wall in the firm. This associate needs to retain access to everything he currently can access, but legally we need to restrict his access to this matter (folder) and all it's contents.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Enable admin settings to customize new user onboarding setup flow

    The new user onboarding displayed at https://{DOMAIN}.app.box.com/onboarding/setupflow should be customizable.

    Currently new users are guided through a one time onboarding set of screens in the web app. These are Box branded and while they personally greet the user are not otherwise configurable.

    This feature should be opt-in, easily disabled by CLI or API (e.g. show-onboarding: False), or allow for customization.

    We can currently enable the promotion of Box Mobile, Notes, etc. in the Admin Console. This would be similar to implement and appropriate on the User Settings console tab.

    Right now the final screen displays a prompt for the user to download Box Drive - an installer that requires admin credentials. If the user doesn't have these, or the organization is discouraging Drive use (esp. for M1 Mac users not currently supported), it can result in a support ticket if the new user assumes this is a necessary step in the process.

    The new user onboarding displayed at https://{DOMAIN}.app.box.com/onboarding/setupflow should be customizable.

    Currently new users are guided through a one time onboarding set of screens in the web app. These are Box branded and while they personally greet the user are not otherwise configurable.

    This feature should be opt-in, easily disabled by CLI or API (e.g. show-onboarding: False), or allow for customization.

    We can currently enable the promotion of Box Mobile, Notes, etc. in the Admin Console. This would be similar to implement and appropriate on the User Settings console tab.

    Right now the final screen displays a prompt for the user… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Users and Groups  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close