Act on Behalf of Another User with Sender Identity
Send and manage signature requests on behalf of another user via the BoldSign API, with explicit authorization, no credential sharing, and a full audit trail.
What is sender identity?
Sender Identity lets an approved user send and manage signature requests on behalf of the identity owner through the BoldSign API.
Requesting authorization
Users can request approval from the identity owner to carry out on‑behalf actions securely.
Manage documents on behalf
Approved users can send documents, track status, and manage the workflow. The identity owner also receives notifications when the document is sent, viewed, signed, or completed.
Secure access control
The identity owner can revoke access at any time.
Getting started
Set up on‑behalf access in minutes. Create a sender identity, receive approval, and start sending and managing documents via the BoldSign API with ease.
STEP 1
Create a sender identity
Use a API call or the web app to create a sender identity by providing the identity owner’s name and email.
STEP 2
Request approval
The identity owner receives an email to approve the sender. Once approved, delegated actions are enabled.
STEP 3
Act on behalf
Use the OnBehalfOf property in your API requests to send documents, trigger reminders, update access codes, and download audit logs on behalf of the identity owner. See our developer documentation for details.
Why sender identity matters
Organizations often rely on assistants to handle contracts. Sender Identity keeps the process secure and consistent.
Secure delegation
Delegate without credential sharing, while maintaining control and compliance.
Operational efficiency
Speed up high-volume agreement workflows with fewer handoffs and less friction.
Consistent branding
Applies the identity owner’s branding so recipients trust the communication.
Security and control
Securely delegate sending without sharing credentials—every action is approved, revocable, and fully audited for complete control.
Explicit consent
Identity owners can approve or revoke access anytime.
User-level access
Permissions are tied to individuals for clear accountability.
Audit trail
Every action is logged for compliance and monitoring.
Common use cases
Built for teams that send on behalf via API and need accountability without shared logins.
Executive workflows
Send NDAs, offer letters, and approvals on behalf of an executive. Manage drafting, sending, reminders, and tracking through the API.
Sales operations
Automatically send quotes and order forms as the assigned rep. Recipients see a consistent sender and branding, and reporting stays accurate.
Operations teams
Centralize recurring sends like renewals, onboarding, and vendor agreements through one integration. Business owners remain the visible sender.
Customer success and renewals
Send renewal agreements on behalf of account owners. Automate reminders or handoffs based on events such as sent, viewed, signed, and completed.
Shared inbox teams
Avoid shared logins. Delegate sending via API with approval, clear accountability, and revocable access.
Platform-driven signing
Your app or middleware drives the signature flow via API. Each business user remains the official sender for a trustworthy recipient experience.
See it in action
Ready to see how Sender Identity fits into your workflow? Discover how teammates can securely send and manage documents as the identity owner with full audit visibility.
Frequently asked questions
You can create a sender identity using either a quick API call or through the web app by providing the identity owner’s name and email. However, note that while identities can be created using both methods, documents are sent only via the API.
No. BoldSign does not support duplicate sender identities across accounts. Each email can only be linked to one account.
Sender identities are user-specific. Only the creator can view or manage them, ensuring privacy and compliance.
No. Account admins do not have access to sender identities created by other users.
No. Sender identities are tied to individual user accounts and cannot be shared or managed at the team level.
The document appears to come from the sender identity’s email. Signers see that email as the sender, and notifications reflect the identity owner’s branding and settings.
The identity will no longer be available for new sends, but past documents will retain the original sender details.
Sign up for your free trial today!
30-day free trial- No credit card required
- 30-day free trial
- No credit card required
