1. What is Box Sign for Salesforce?
Box Sign for Salesforce lets users send, track, and manage electronic signature requests directly from Salesforce, without leaving the platform. It integrates with Salesforce records so signing workflows are tracked alongside your business data. Learn more: Using Box Sign in Salesforce
2. How do I send a Box Sign request from Salesforce?
You can send requests using:
The Send Box Sign button on object pages (Creating the Box Sign button in Salesforce)
A Flow action (“Send Box Sign Request”)
Programmatically via the toolkit method
BoxSignService.sendSignRequests
3. How do I track the status of Box Sign requests?
In Box: Box Sign home page
In Salesforce: Signs related list on object records
4. Can I pre-fill signer information or add document tags?
Yes, admins can pre-fill signer info and map Salesforce fields to document tags when configuring the Box Sign for Salesforce. This speeds up sending and reduces manual errors. Learn more on how to set this up: Setting up advanced Sign settings
5. Can I send a signature request to a group instead of to a single recipient?
Yes. Box Sign for Salesforce supports recipient groups, which allow you to send a signature request to multiple recipients while requiring only one member of the group to complete the action. When one recipient completes the action, the signature request automatically progresses to the next step in the workflow.
6. Which Box plans support CAC/PIV authentication for Box Sign?
CAC/PIV (Common Access Card / Personal Identity Verification) authentication is available only on Enterprise Plus and Enterprise Advanced plans. In addition, customers must be provisioned on the Box Sign CAC/PIV Add-On Pack to enable this verification method. For more details on CAC/PIV authentication, see CAC/PIV E-Signature Authentication.
7. Which Box plans support Box Login authentication for Box Sign in Salesforce?
Box Login is an extra layer of security provided by Box Sign allowing senders to apply additional recipient authentication methods by requiring the recipient to log in to their Box account before starting the signing process. Box Login as an additional Box Sign verification method is available only on the Enterprise Plus and Enterprise Advanced plans. Learn more: Additional Recipient Authentication
8. Can admins control which Sign recipient verification methods are available in Salesforce?
Yes. Salesforce admins can manage which Box Sign recipient verification methods are available to users when sending Box Sign requests from Salesforce. This can be configured in: Box Salesforce Settings → Advanced Setup → Box Sign Configuration.
From there, admins can enable or disable specific verification methods (such as SMS Authentication, Box Login or CAC/PIV) to align with specific organizational requirements.
9. Are there any signing order requirements when using CAC/PIV authentication?
Yes. When CAC/PIV authentication is used in a signature request with multiple recipients or verification methods, the recipient using CAC/PIV must be placed last in the signing order.
10. Can CAC/PIV authentication be selected for multiple recipients in a single request?
No. CAC/PIV authentication is limited to a single recipient per signature request. This recipient must also be the final signer in the signing order.
11. Can CAC/PIV authentication be applied to recipient groups?
No. CAC/PIV authentication is not supported for recipient groups. It can only be assigned to an individual recipient.
12. Why isn’t my Box Sign record updating in Salesforce?
Updates on the document status may not flow if:
- The connected app is not authorized for the user
- Profiles or Permission Sets are missing access to the connected app
- Real-time events are delayed
Ensure that you configure the profiles and permission sets access according to these instructions.