Invite team members to your workspace

Inviting teammates is not only an access task. It is a workflow design task. The choices you make during onboarding affect envelope quality, routing consistency, and how quickly pending signatures are recovered. This guide explains how to invite users through Users & Invitations while protecting process quality as your workspace scales.

If your workspace is brand new, complete Set up your workspace first. Folder structure and naming conventions should exist before a large group starts sending documents.

Plan before you send invitations

Begin with a simple onboarding plan for the first thirty days. Define who will create envelopes, who reviews drafts, who sends reminders, and who owns template maintenance. Without this, new users often create overlapping templates or inconsistent role names. That confusion is difficult to undo once usage grows.

A useful plan includes three cohorts: pilot senders, backup senders, and status-only users. Pilot senders receive full training on Create Envelope and Send Envelope. Backup senders shadow the pilot group, then take turns. Status-only users learn envelope tracking and reminder actions without being expected to author new templates.

Step 1: Open Users & Invitations

In the workspace sidebar, open Users & Invitations. Review current active and pending entries. Confirm you are working in the correct workspace if your account belongs to more than one. Send invitations in controlled batches so you can support questions without overwhelming your team.

Step 2: Invite the pilot cohort

Add the first group of users who will execute live workflows this week. Enter each email carefully and double check domain spelling before sending. Keep this group small enough that onboarding support can be quick. A pilot of three to eight users is common for operations and legal teams.

Share a short message with each invitation wave that includes your naming conventions, first template to use, and links to internal guide standards. This creates alignment before users click around the interface on their own.

Step 3: Validate acceptance and first login

Track invitation acceptance daily during rollout week. When users move from pending to active, ask them to complete one check-in flow: open Envelopes, confirm folders, and view template list. This confirms they landed in the right workspace and can navigate the expected areas.

If invitations are not accepted, use the help-center troubleshooting pages: /help-center/invite-users-to-workspace and /help-center/accept-workspace-invitation. Save these links in your onboarding message template.

Step 4: Train users on exact app labels

During onboarding sessions, use the exact UI language your team sees on screen. Teach users to start with Create Envelope, then navigate Details, Documents, Roles, Fields, and Review. If they send from templates, show Use Template, Quick Send, and Customize Before Sending. If they need to save a repeating workflow, show Save Template.

Consistent terminology reduces internal support noise. People can ask better questions when they reference visible labels instead of ambiguous phrases like stage two or signer page. It also makes guide documentation easier to maintain as your process matures.

Step 5: Assign operational ownership per user

Onboarding is successful when responsibilities are explicit. Assign document owners for each active process. Document owners should know how to prepare envelopes, monitor status, and use Send Reminder when signers stall. Backup owners should know how to continue the process when someone is out.

For teams using templates, assign one person as template maintainer. That person approves structural edits and version updates. This prevents a common failure mode where many users edit templates independently and field placement drifts over time.

Step 6: Run first live send with each cohort

Ask every invited sender to complete one live envelope flow in the first week. Keep documents simple and include known test recipients where possible. Review the resulting envelope together. Confirm role assignments, field accuracy, and handoff clarity. If issues appear, fix the runbook quickly before onboarding the next cohort.

New senders should practice both paths: Create Envelope and template-based sending with Use Template. Reference Create and send envelope and Send from template: Quick Send vs Customize during this exercise.

Handle invitation issues with a standard response flow

When a user cannot join, avoid ad-hoc troubleshooting. Use a fixed sequence. First, confirm email spelling and workspace context. Second, resend the invitation. Third, ask the recipient to search spam and quarantine folders. Fourth, share the acceptance article. Fifth, escalate to your internal admin if the address belongs to a restricted domain with strict mail filtering.

This sequence is repeatable and easy for support leads to teach. It also prevents premature assumptions that the platform is failing when the issue is usually delivery filtering or account mismatch.

Rollout metrics to track in month one

Track adoption with a short dashboard. Useful metrics include invitation acceptance rate, first envelope completion rate per cohort, average time from invitation to first send, and reminder usage per active sender. These signals tell you whether training is clear or whether friction remains in specific steps such as Fields assignment.

Review metrics weekly and adjust your onboarding kit. If most questions cluster around one step, update that section in your runbook with clearer screenshots and precise labels.

Invitation rollout checklist

1. Define cohorts and responsibilities for each group.
2. Open Users & Invitations and confirm workspace context.
3. Send pilot invitations and monitor acceptance daily.
4. Train on app labels and one complete send flow.
5. Assign owners for reminders and template upkeep.
6. Run first live send for each new sender.
7. Track metrics and refine onboarding runbook weekly.

What to do next

Once your first team cohort is active, move to document quality and routing consistency. Continue with Configure signing fields on a PDF and Sequential signing order. These two guides reduce rework and keep handoffs predictable as team usage increases.