Anonymous
My feedback
121 results found
-
26 votes
Anonymous
shared this idea
·
-
49 votes
Anonymous
supported this idea
·
-
1 vote
Anonymous
shared this idea
·
-
12 votes
An error occurred while saving the comment
Anonymous
supported this idea
·
-
7 votes
Anonymous
shared this idea
·
-
2 votes
Anonymous
shared this idea
·
-
4 votes
Anonymous
shared this idea
·
-
6 votes
Anonymous
shared this idea
·
-
11 votes
Anonymous
shared this idea
·
-
64 votes
Anonymous
supported this idea
·
-
92 votes
We are planning improvements to how we handle Japanese language queries but this work is not currently on the roadmap in the next 12 months. We will take this into consideration for the annual roadmap for next year.
Anonymous
supported this idea
·
-
10 votes
Anonymous
shared this idea
·
-
60 votes
We have already made sure that the Content remains available to all the collaborators during a Transfer & Delete LFO. We are working on ways to do the same with other forms of LFO. We believe this approach will be a much better productivity accelerator for our customers.
For the purposes of this request to allow for email notification, this still remains in our roadmap to evaluate what would be the remaining use cases that will required an email to be sent.
Anonymous
supported this idea
·
-
2 votes
An error occurred while saving the comment
Anonymous
commented
By adding this feature, we can prohibit the creation of folders while granting invitation rights.
This will prevent collaborators with co-owner and lower permissions from creating folders, which will prevent unnecessary subfolders from being created and will be easier to control.
<フォルダの設定に「サブフォルダを作成できるのは所有者のみ」という設定を追加してほしい>
この機能を追加することで、招待権限を与えつつフォルダの作成を禁止することができます。
これにより共同所有者以下の権限をもつコラボレータはフォルダを作成することができなくなるため、不要なサブフォルダの作成ができなくなり統制がしやすくなります。
Anonymous
shared this idea
·
-
4 votes
Anonymous
shared this idea
·
-
22 votes
Anonymous
supported this idea
·
-
11 votes
Anonymous
shared this idea
·
-
11 votes
Anonymous
supported this idea
·
-
84 votes
We are definitely tracking this feature, but it is not yet on the roadmap for delivery.
How would envision managing your groups?
Would you want to sync with an existing directory, or create the Groups directly in Box?
Anonymous
supported this idea
·
-
62 votes
Anonymous
supported this idea
·
We are using a workflow for a plan document, and sometimes a plan is cancelled in the middle of the workflow.
The workflow itself cannot be deleted because it is used in other plans, but we would like to terminate the workflow that has been canceled because it would be confusing to leave it in the middle of a workflow.
We know that it is not possible to stop events that move automatically, but for workflow events such as approval tasks that are actually performed by the person in charge, we would like to set a deadline for approval and terminate the workflow if no action is taken within the deadline, or we would like to see the addition of a "Cancel" button in addition to the existing "Approve" and "Reject" buttons, and for the "Cancel" button to be selectable by both the requester and the approver, or some other function to cancel the workflow midway through the process.
<ワークフローをキャンセルする機能の追加依頼>
計画書のワークフローを使用しており、ワークフローの途中で計画が中止になることがある。
他の計画書でも使用するため、ワークフロー自体は消せないが、計画が中止になったワークフローは途中の状態で残しておいても紛らわしいため終了させたい。
自動で動くイベントについて止めることができないのは承知しているが、実際に担当者が物理的な操作を行う承認タスクなどのワークフローのイベントに関しては承認までの期限を設け期限内に操作がなければワークフローを終了する設定や、既存の「承認」・「拒否」ボタンの他に「キャンセル」ボタンを追加し、「キャンセル」ボタンについては、依頼者、承認者どちらも選択できるようにするなど、ワークフローを途中でキャンセルする機能を追加してほしい