Set up your WoltSign workspace

A clean workspace setup saves time on every envelope you send. Teams often focus on sending speed first, then discover inconsistency in folder names, role naming, and invitation practices. This guide gives you a practical setup sequence you can complete in one working session. You will define structure, align your team on labels, and leave with a repeatable process for both one-off envelopes and template-driven workflows.

If you are migrating from email attachments or shared drives, treat this as an operational reset. Decide who owns setup decisions, what naming standard your team will follow, and where troubleshooting links live. For sending mechanics, review Create and send envelope after this guide.

Step 1: Confirm workspace ownership and scope

Before inviting anyone, decide who owns workspace configuration. In small teams, this is usually one operations lead. In larger teams, one owner and one backup is safer. Write down which document families belong in this workspace, for example sales agreements, onboarding packets, or vendor approvals. Keep scope clear so teammates know whether to create folders here or in another workspace.

Step 2: Create your folder taxonomy first

Folder decisions are hard to fix after hundreds of envelopes. Open Envelopes and define folders around how your team actually searches later. Good patterns include by business process, by region, or by document class. Avoid overly granular names early. You can split later once volume proves a need. This keeps navigation simple for new team members.

A practical starter set is Inbound Requests, Outbound Contracts, Renewals, and Archive Ready. If you need examples, compare with Organize envelopes with folders and the troubleshooting article at /help-center/envelope-folders-and-statuses.

Step 3: Define naming conventions for envelopes and templates

Your title format should answer three questions at a glance: what document this is, who it is for, and when it was initiated. A reliable pattern is document type plus counterparty plus date. Keep it short enough to scan in list views. Do the same for template names so users can quickly distinguish one process from another.

Write your naming standard in a short internal note. Include examples of good and bad titles. This tiny investment prevents duplicate work because teammates can find old envelopes before creating new ones. Consistent names also improve audit conversations when someone asks how a document moved from draft to completion.

Step 4: Set team access through Users & Invitations

Open Users & Invitations and add teammates in small batches. Invite only people who need immediate access for current workflows. Too many early invites can create noise when users are not yet trained. As invitations are accepted, verify each person appears under active users and can reach the expected sections in the sidebar.

If an invitee cannot join, use these troubleshooting references: /help-center/invite-users-to-workspace and /help-center/accept-workspace-invitation. Keep those links in your internal runbook so team leads can self-serve common issues.

Step 5: Build one baseline template before broad rollout

Even if most sends are one-off, a baseline template helps teams learn the role and field model correctly. Pick a frequently used document and create a reusable version with clear role names. This becomes your training artifact and your quality reference. Use Save Template when the first workflow is stable.

Start simple. One sender-facing guide can cover how to open Use Template, when to pick Quick Send, and when to choose Customize Before Sending. The related deep dives are Create a reusable template and Send from template: Quick Send vs Customize.

Step 6: Run one complete envelope walkthrough as a team

Open Create Envelope and walk teammates through Details, Documents, Roles, Fields, and Review. Ask one person to narrate every click while others verify naming and role ownership. This reveals confusion points early, such as vague role labels or missing field assignments. Use a real document and test recipient emails so your team sees a realistic flow.

During this exercise, enforce exact UI language. Use Details instead of metadata, Roles instead of participants, and Send Envelope as the final action label. Shared vocabulary reduces training friction and helps support messages stay precise.

Step 7: Define reminder and follow-up ownership

Decide who sends follow-ups when signers stall. A common model is document owner sends first reminder, operations backup sends second reminder after a fixed interval. Put this into your runbook with concrete timing. When this is unclear, envelopes stay pending because everyone assumes someone else will nudge signers.

Use Send Reminder from envelope detail and track by status. For the full operational pattern, read Track signers and send reminders.

Step 8: Establish a monthly cleanup routine

Healthy workspaces drift unless someone maintains them. Once per month, review folder usage, archive stale drafts, and retire duplicate templates. Keep a short changelog of what was cleaned and why. This helps new admins understand current standards and prevents reintroducing old naming patterns that caused confusion.

Include user audit checks too. Remove people who no longer need access and follow up on pending invitations older than your onboarding threshold. A clean member list reduces mistakes when sharing documents or assigning roles in urgent sends.

Recommended rollout checklist

1. Assign one workspace owner and one backup owner.
2. Create core folders and document naming standards.
3. Invite first user cohort through Users & Invitations.
4. Build one reusable template and validate role labels.
5. Complete one full Create Envelope walkthrough with the team.
6. Publish reminder ownership and response timing.
7. Schedule monthly workspace hygiene review.

What success looks like after setup

You know setup is working when new teammates can send confidently without private coaching, envelope lists are easy to scan, and reminder ownership is obvious. The goal is operational predictability. Senders should spend time on document quality, not on guessing where controls live in the app.

Next, move to the flagship walkthrough at Create and send envelope to standardize execution from draft to completion.