A
Action type: what a recipient does with a package: Signer, Viewer or CC. A template role has an action type too. See Building a workflow. Active: the template status that allows it to be used. A template starts asDRAFT and can also be ARCHIVED. See Templates.
API key: a bearer token that lets your own code call the Flowsign REST API. Each key is issued for one role and one workspace, acts with that role’s permissions there, and is shown once. Only an Owner can create or revoke keys, and the API needs the Enterprise plan. See API keys.
Audit trail: the record of every event on a package (who opened, signed or declined, and when) and, as a report, every recorded member and signing event across the organisation. See Audit trail.
B
Bulk send: one package per row of a list, all from the same template. It only sends from a template and needs the Business plan or higher. See Bulk send.C
CC: a recipient who receives the finished copy by email only, and never gets a signing session. See Getting started. Certificate of completion: the record Flowsign produces when the last recipient finishes, available from the package page alongside the finished documents. See Getting started. Coming soon: a release label marking something planned and visible in the app but not usable yet. Its controls are shown and disabled. See Release labels. Contact: a person or company you send to, added automatically when you send packages or by hand, and organised into companies, groups, lists and labels. See Contacts. Correction: changing a sent package. A package mid-correction shows a correction tag in its header, and corrections are only offered when the package’s status and your permissions allow them. See Package detail. Custom field: an organisation-defined value senders fill in on a package, such as an employee ID, with a key that never changes and that integrations read it back by. Enterprise plan; the page is currently marked Coming soon. See Custom fields.D
Declined: the package status after a recipient declines to sign. Declining asks for a reason and cannot be undone. See Signing a document. Delivery: one HTTPPOST of a webhook event to an endpoint. Each carries a stable delivery id, is signed with the endpoint’s secret, and is retried with backoff until it succeeds or is exhausted. See Webhooks.
Document type: the per-document choice between Standard (uploaded as-is and flattened to a PDF) and Dynamic (a .docx whose wording can change per send, labelled Experimental). See Document types.
E
Endpoint: a webhook endpoint, an HTTPS URL Flowsign POSTs to when a package or session changes. Endpoints belong to the organisation and receive events from every workspace. See Webhooks. Experimental: a release label on a feature that is available now and still being shaped. Today it appears on Dynamic documents. See Release labels. Expiry: the point at which an unsigned package ends. Set with Expire after on a template, or a Duration on a package. An expired package is voided and raises thePACKAGE_EXPIRED event. See Building a workflow and Events.
External id: an id of your own passed when creating a package through the API. Repeating the call with the same external id returns the existing package instead of creating another. See Developer quickstart.
F
Field: something a recipient completes on a page: Signature, Initial, Date, Name, Email, Company, Title, Text, Number, Checkbox, Radio or Dropdown. Each field is assigned to a recipient (or a role) and can be required. See Fields editor.I
In-person signing: hosting a recipient’s session on the sender’s own device, started from a package’s Sign in person action. The recipient signs under their own session, so the audit trail behaves as it would from an emailed link. See In-person signing. In progress: the API status of a package that is out with recipients. The packages list shows it as Sent. See Sent packages.L
Library: a shared, foldered store of documents for your organisation, separate from any one package, ready to attach to packages, templates and bulk sends. See Library.M
Member: a person in your organisation, with a workspace and a permission profile. Members count towards your plan’s seat limit. See Members. Merge field: a named value on a template (for examplestart_date) supplied at send time and interpolated into the template’s name, email copy and Dynamic documents. Each has a key, a label, an optional default and a required flag. See Building a workflow.
O
On hold: a paused package. Its signing links stop working and nobody new is invited until it is resumed, when the expiry moves back by the time spent on hold. See Developer quickstart. Organisation: your Flowsign account as a whole: name, plan, billing, branding and security, plus every workspace and member. See Setting up your organisation. Owner: the locked, organisation-level role that sits above every workspace. An Owner has every permission everywhere, and only an Owner can invite members, manage billing and security, create workspaces and custom roles, and create API keys. An organisation must always keep at least one. See Roles & Permissions.P
Package: one send: a set of documents, the recipients who act on them, and the signing sessions that result. See Packages. Permission profile: the set of permissions a member holds in a workspace: Admin, Sender, Viewer, or a custom role cloned from one of them. Also called a workspace role. See Roles & Permissions. PowerForm: a public link to a template. Anyone with the link can open it, fill in their details and sign without being added as a recipient first, up to an optional submission limit. Business plan or higher. See PowerForm.R
Recipient: a person on a package, with a name, an email address and an action type. See Getting started. Release label: the Experimental or Coming soon chip beside a feature, describing how finished it is. A label never changes a package’s status or audit trail. See Release labels. Reminder: the follow-up email sent to a recipient who has not finished. Set as Send reminder after on a template, Reminder Frequency on a package, or sent by hand with Send reminder. See Building a workflow. Role: on a template, a named slot such as Employee or Manager that a person fills at send time. Fields are placed against a role, and the API matches recipients to roles by name. Not to be confused with a permission profile. See Building a workflow.S
Session: one recipient’s turn on a package, created when the package is sent. Its status isWAITING, ACTIVE, COMPLETED, DECLINED or CANCELLED, and sessions are what webhook session events report on. See Events.
Share link: in the API, a package’s read-only preview link, returned by POST /api/v1/packages/{packageId}/share-link. Anyone with the URL can view the package, so treat it as a secret. Distinct from sharing a package with a colleague. See Get a preview link.
Sharing a package: giving a team member View, Edit or Manage access to one of your packages from its preview panel. Shared packages are tagged Shared with you. See All packages.
Signer: a recipient who completes the fields assigned to them. See Getting started.
Signing group: a set of members intended to complete a recipient’s step between them, so any one of them can sign instead of a named person. Groups and members can be managed now; packages cannot yet be addressed to one. See Groups.
Signing mode: how a template’s roles act: Parallel signing (everyone at once), Sequential signing (one at a time, in role order) or Workflow. See Building a workflow.
Signing order: the package setting that makes recipients act one after another, each emailed when it is their turn, instead of all at once. See Create a package.
Signing secret: the per-endpoint secret shown once when a webhook endpoint is created, used to verify each delivery’s HMAC-SHA256 signature. See Webhooks.