Organisation and workspaces
Your organisation is the account: its name, plan, billing, branding and security live at this level. See Company and Organisation security. An organisation is divided into workspaces: offices, regions or teams, each with its own packages, templates, contacts and members. Every organisation has a default workspace; extra workspaces need the Enterprise plan. See Workspaces. Members join a workspace with a permission profile (also called a workspace role): Admin, Sender, Viewer, or a custom role cloned from one of them. Owner is different: a locked, organisation-level role that sits above every workspace. An Owner has every permission everywhere, and only an Owner can invite members, create workspaces and custom roles, manage billing and security, and create API keys. See Members and Roles & Permissions.Packages
A package is one send: a set of documents, the recipients who act on them, and the signing sessions that result. See Packages.
With signing order off, everyone is invited at once. With it on, recipients act one after another and each is emailed when it is their turn. See Create a package.
Recipients and sessions
A recipient is a person on a package, with a name, an email address and an action type: a Signer completes the fields assigned to them, a Viewer reads the package while it is out and has no fields, and a CC recipient receives the finished copy by email only. A session is one recipient’s turn on a package, created when the package is sent. It moves throughWAITING, ACTIVE, COMPLETED, DECLINED or CANCELLED, and sessions are what webhooks report on. A view link gives read-only access to the documents for someone who does not sign. See Signing a document and View links.
A signing group is meant to stand in for a named person, with any one member completing the recipient’s step; groups can be set up now, but packages cannot yet be addressed to one. See Groups. A sender can also host a session on their own device for a recipient who is with them: In-person signing.
Templates and roles
A template is a reusable package definition: documents, named roles, fields, merge fields, email copy, reminder and expiry settings. Instead of naming people, it defines roles (for example Employee and Manager), and you fill in who plays each role when you send. Through the API, recipients are matched onto roles by name, not by position. A template starts asDRAFT and must be ACTIVE before use. The package copies the template’s documents and fields, so later edits to the template do not reach packages already sent. See Building a workflow and Template builder.
A template’s roles carry its signing mode: parallel, sequential, or Workflow, where answers to questions decide which documents go out and who signs. See Workflow signing.
Merge fields and custom fields
A merge field belongs to a template: a named value (for exampleemployee_name) supplied at send time and interpolated into the template’s name, email copy and Dynamic documents. A blank value takes the field’s default.
A custom field belongs to the organisation: senders fill it in on a package and integrations read it back by key as the package’s metadata. Enterprise plan, and the page is currently marked Coming soon. See Custom fields.
Documents and the library
A document is one file in a package or template, with fields placed on its pages and assigned to a recipient or role in the Fields editor. A Standard document is uploaded as-is and flattened to a PDF; a Dynamic document is a.docx whose wording can change per send, and is labelled Experimental. See Document types.
The Library is a shared, foldered store of documents, separate from any one package, ready to attach to packages, templates and bulk sends. See Library.