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.
13 results found
-
Dynamically name signed documents based on metadata: signer's full name, company, email and others
When there are documents in the same folder or templates that are repeatably signed with the same name (Ready Sign Link, Batch Send), Box Sign adds a number and () to the filename to note the different/unique files.
There needs to be a better way to name the files - perhaps using metadata or using the unique id of the sign request. And then all files - signed docs and signed log would be renamed with the same name. Otherwise it's very hard to tell files apart when they all have the same name with just a number and ()…
90 votes -
Save password settings in template definitions
I would like to be able to save password settings for each recipient in the template definition.
If a customer-specific template has been defined and a password has been agreed upon with the customer, this will save the time and effort of setting a password each time.(Japanese)
テンプレート定義に受信者ごとのパスワード設定を保存できるようにして欲しい。
顧客専用のテンプレートが決まっており、かつ、顧客との間でパスワードの取り決めもなされている場合、毎回パスワード設定を行う手間が省けます。19 votes -
When creating a sign template,I want to specify a location for saving requests in a folder different from where the template is saved.
When creating a sign template, I want to specify a location for saving requests in a folder different from where the template is saved.
Currently, when a request save location is specified in a template, the template is also saved in the specified request save location.
If I move the template file to another folder, the request save location set in the template will also change to the destination folder.
I don't want to re-specify a different folder to save the request each time I create a sign request from a template.
サインテンプレート作成時テンプレートの保存場所とは別のフォルダにリクエストの保存場所を指定したい。
現在、テンプレートでリクエストの保存場所を指定すると、テンプレートも指定したリクエストの保存場所に保存されます。
テンプレートのファイルを別のフォルダに移動するとテンプレート内に設定したリクエストの保存場所も移動先のフォルダに変わってしまう。
テンプレートからサインリクエストを作成するたびにリクエストの保存場所を別のフォルダに指定しなおすのは避けたい。
30 votes -
Retain "Request Viewed" timestamps on cancelled & expired Box Sign envelopes
We are not able to easily see the View history on cancelled or expired Box Sign envelopes -- it only reads "Cancelled" rather than "Request Viewed," so it is unclear if the recipient saw the document prior to its cancellation. This would be extremely helpful for confidential documents, etc.
1 vote -
Box Sign - Fields filled out become metadata
Box Sign - Fields filled out become metadata
56 votes -
Salesforce Integration with CFR Part 11
if a CFR-enabled user is initiates a request from the SFDC integration, that request should be CFR-compliant.
1 vote -
Box Sign requests default "my requests" folder
Box Sign requests default to save into a "my requests" folder for all users. We don't always need the sign request saved into our regular Box folder structure and having a separate place for each user to send their requests to would be more beneficial.
28 votes -
Box Sign: Document ID on the header/footer of the document
We would like to add the Document ID number on the header or footer of the documents when we finished signing with Box Sign. We understand that the hard copy is not required as long as the sign is done with Box Sign. But, if we print out the signed document, we can not see any evidence that the signed page is related to the other pages. In the DocuSign, I can see such function.
1 vote -
Restrict Box Sign to internal use only
[Request contents]
Please add the ability to restrict recipients to Box Sign "options".
I would like the scope of restrictions to be selectable only by internal users and invited users, similar to shared links.[Background]
If you restrict Box Sign to internal use only, security incidents may occur without the above features.(Japanese)
[リクエスト内容]
Box Signの"オプション"に受信者を制限する機能を追加してほしい。
制限する範囲は、共有リンクと同様に社内ユーザーと招待されたユーザのみが選択できるようにしてほしい。[背景]
Box Signを社内利用のみに制限している場合、上記の機能がない場合セキュリティインシデントが発生する可能性があるため。53 votes -
Conditional Fields Functionality
Provide conditional field functionality that will only allow certain fields appear to the recipient when a specified condition is met.
92 votesThe Product Team is considering this request for development the next year. Please share additional feedback and use cases to help us understand what functionality is the most needed and how it's going to be used.
-
Box Sign - Combine Executed Signed Docs and Signature Log
Currently, when you send a document to be signed, the signed executed document and signature log are saved as separate files. It would be nice if the signed doc and signature log were one document and saved as an updated version of the original document. Currently, it turns 1 document into 3 documents, and clutters up the folders.
39 votes -
Allow non-Box users to save their signatures for use with Box Sign for re-use.
Non-Box users, especially in a platform scenario currently need to "create" a signature each time they are asked to sign something. A lot of these users are signing many requests a day/week and would save time if they were able to save their signature somehow.
4 votes -
Make 2FA via SMS in Box Sign the First Step, Not Last
Box Sign offers a 2F authentication method via SMS, however, on the signer does not have to complete the 2FA until the very last step. This poses challenges for our use case as we have PHI data on the documents requiring signature so we need this authentication to occur FIRST rather than LAST to ensure that we have authenticated the user before they can even view the document.
10 votes
- Don't see your idea?