Configure Dropbox Sign organization settings
Customize your Dropbox Sign organization by managing branding, document settings, and organization-wide controls.
7 min de lectura
Your organization is up and running in Dropbox Sign. Now it's time to decide how it should look, who can do what, and how it should be managed.
The Settings section of the Admin console is where you'll configure those organization-wide preferences.
In this module, you'll explore the settings that shape how Dropbox Sign works across your organization.
Because many of these settings apply to all users, it's important to understand their impact before making changes.
Branding
Branding allows you to customize the signing experience for your organization.
Consistent branding helps create a more professional experience for signers while reinforcing trust and brand recognition.
To manage branding settings:
Open the Admin console.
Navigate to Settings.
Select General.
From here, you can customize several organization-wide branding elements.
Before reviewing each setting, think about the experience from your signer's perspective. When someone receives a signature request from your organization, they'll see your sender name, logo, and any custom messaging you've chosen. After completing the document, they may also be redirected to a webpage of your choice.
The settings below allow you to customize different parts of that experience.
Logo
Upload your company logo to display on signature requests and signer communications.
Using a recognizable logo can help signers identify legitimate requests from your organization.
Email tagline
Add a short message that appears in communications sent from Dropbox Sign.
This can reinforce company messaging or provide additional context for recipients.
Sender name
Customize how your organization appears to signers when signature requests are delivered.
A consistent sender name can help reduce confusion and improve recognition.
This is especially useful if your organization's legal name differs from the name customers, partners, or employees know you by. When possible, use the name your signers will recognize most easily.
Email signature
Add a standardized email signature to communications generated through Dropbox Sign.
This helps maintain consistency across teams and departments.
URL Forwarding
Admins can configure a destination URL that signers are redirected to after completing a document. This can help create a more connected experience by guiding signers to the next step in the process.
For example, a new employee could be sent to an HR portal after signing onboarding documents, or a customer could be redirected to a confirmation page after completing an agreement.
Important
Changes made in the Admin console apply across your organization.
Updates made in an individual user's account settings only affect that user's experience.
In addition to shaping the signer experience, admins can configure settings that support compliance and regulatory requirements.
eSign disclosure
eSign Disclosure presents signers with a disclosure statement before they complete a signature request. It helps ensure signers understand and consent to the use of electronic signatures.
Depending on your industry, region, or compliance requirements, enabling this setting may be an important part of your signing process. If you're unsure whether your organization requires eSign Disclosure, check with your legal or compliance team before making changes.
To enable eSign Disclosure:
Open the Admin console.
Navigate to Settings.
Select Signature requests.
Enable eSign Disclosure.
Once enabled, signers will be prompted to accept the disclosure before they can sign.
Restricting template creation
Templates help teams standardize recurring document workflows.
However, not every organization wants every user creating or modifying templates.
Depending on your compliance requirements, you may choose to limit template creation to admins.
When to allow template creation
Allowing users to create templates may be appropriate when:
Teams frequently create their own documents.
Departments manage independent workflows.
Flexibility is more important than centralized control.
Examples:
Small organizations
Fast-moving operational teams
Decentralized business units
When to restrict template creation
Restricting template creation may be appropriate when:
Documents require legal review.
Compliance requirements are strict.
Template consistency is critical.
Multiple teams use the same approved documents.
Examples:
HR onboarding packets
Regulatory forms
Standard customer agreements
By limiting template creation to admins, organizations can help ensure that approved templates remain accurate and consistent.
Note
When template creation is restricted to admins, team members can no longer create templates or access the template gallery. This helps ensure templates are managed and maintained centrally.
Data residency
Data residency allows organizations to choose where completed document data is stored.
By default, account data is stored in the United States. Depending on your business requirements, you may choose a different storage location.
Available regions may include:
United States
European Union
United Kingdom
Australia
Canada
Japan
Important
Data residency is configured from the Settings section of the Admin console, not from Security settings.
Note
Organization admins can grant team admins permission to manage document storage locations. This allows teams to manage their own data residency settings while maintaining organizational oversight.
Multi-team data residency
Organizations using Multi-teams can configure data residency at the team level.
This allows different teams to store documents in different geographic regions based on business or regulatory requirements.
For example, a team operating in the European Union may be required to store documents within the EU, while a team in the United States may not have the same requirement.
By configuring Data Residency at the team level, organizations can align document storage with the needs of each business unit rather than applying a single setting across the entire organization.
This flexibility can help global organizations meet regional compliance and data handling requirements.
When might this be useful?
Consider team-level Data Residency when:
Different regions have unique regulatory requirements.
Business units operate in separate jurisdictions.
Data storage requirements vary by geography.
Governance Tip
As your Dropbox Sign deployment grows, governance becomes increasingly important.
Best practice
Use centralized templates and restricted template creation when document consistency, compliance, and legal review are important.
This approach helps:
Reduce duplicate templates.
Maintain approved language.
Improve consistency across departments.
Support compliance requirements.
As your account grows
As your Dropbox Sign deployment grows, a few simple habits can help keep your account organized and easy to manage:
Review your template library periodically and remove outdated templates to help ensure senders are using the correct documents.
Keep branding settings up to date so signers see the correct sender name, logo, and messaging.
Make sure at least two people in your organization have admin access to avoid disruptions if an admin changes roles or leaves the company.
Your organization is starting to take shape. You've configured how Dropbox Sign looks, how teams work together, and how documents are managed across the business.