Branding and settings overview

Where to configure

Branding and organization settings are available under /einstellungen. The feature is intended for Pro and higher plans as well as administrative roles. Personal avatars are managed under /konto.

What you control

• Backgrounds for login, upload and download (max. 5M)
• Email logo (max. 1024k)
• Colors
• Welcome title
• Email signature and subject
• SMS text
• Personal avatar under /konto

Practical guide for day-to-day use

Set the feature up so it fits your workflow: define who is responsible, which deadlines apply, and how files land in your internal archive after the exchange. Communicate expectations to participants in writing – short notes on permissions, validity and download behavior prevent most follow-up questions.

Test critical paths yourself once (create, share, guest access, completion). Document deviations and update internal short guides. That way Secure File Transfer remains a controlled part of your processes.

Checklist

• Admin permissions
• Assets prepared
• Limits known
• Review planned

Further guidance

Plan shares and access deliberately. Before sharing links, check roles, deadlines and security options. Store important results outside the platform if you need them long term. Train new colleagues using this help article and related topics.

If anything is unclear, use related articles in the help center or the contact form. Avoid assumptions about features not described here – especially ZIP downloads, SMS codes for guests, or qualified electronic signatures.

Keep internal processes lean: a few clear standards for naming, deadlines and archiving work better than many exceptions. Regularly check whether expired access has been ended and required files have been secured. Document exceptions in writing so your team works consistently.

Use product features as described here: individual downloads in Collect, email code instead of SMS for Sign guests, and no QES or legal-certainty claims. That keeps help and practice consistent.

Going deeper in daily operations

Define binding standards for your team: who may share links, which deadlines apply by default, and where completed files are archived. Write these rules down briefly and link the matching help articles. That avoids contradictory answers to customers and partners.

Before every larger rollout, walk the critical paths yourself once: create, share, guest access, completion and archiving. Note deviations and update your internal quick guide. Also plan regular reviews for expired access, open signatures and collections nearing their end.

Communicate feature limits clearly – especially individual download instead of ZIP in Collect, email code instead of SMS for Sign guests, and avoiding QES wording. Clear expectation management saves support effort and protects your reputation.

If something remains unclear, use related articles or the contact form. Extend processes only where the product actually offers the described feature.