> ## Documentation Index
> Fetch the complete documentation index at: https://docs.safeclose.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Run a signing workflow from start to finish in Safeclose

> Step-by-step instructions for managers creating and monitoring signing packages, and signers reviewing and completing their assigned documents.

Safeclose's signing workflow connects two groups of people: **managers** (and admins) who create and oversee signing packages, and **signers** who review and electronically sign their assigned documents. Both roles access the same Signing hub at `/signing`, but see different views based on the capabilities granted by their signing role.

When you sign in for the first time, Safeclose shows a guided onboarding walkthrough tailored to your role. Complete it to unlock the full hub — you can dismiss it at any point and it won't reappear on the same device.

<Tabs>
  <Tab title="Manager: create and monitor a package">
    ## Create a signing package

    Managers with **write** access to signings can create new packages from the Manager view.

    <Steps>
      <Step title="Go to the Signing hub">
        Click **Signing** in the main sidebar. Safeclose redirects you to the Manager hub at `/signing/manager/signings`.

        <Note>
          If you see the onboarding walkthrough instead, complete or dismiss it first. The hub becomes available immediately after.
        </Note>
      </Step>

      <Step title="Select a location">
        In the **Create draft signing** form, choose the location where this signing will take place. Locations are set up by your organization admin under **Organization settings → Locations**.

        If your account has access to only one location, it is pre-selected.
      </Step>

      <Step title="Attach a flow (optional)">
        Select a signing flow from the dropdown to associate a pre-built document flow template with this package. Flows are filtered to match the location you chose in the previous step. Leave this blank if you are building the package manually.
      </Step>

      <Step title="Submit">
        Click **Create draft signing**. The new package appears in your signings list with status `draft`.
      </Step>
    </Steps>

    ## Monitor and manage a package

    Click **Open** next to any signing in the list to view its detail page. From there you can:

    * **View documents** attached to the package and their template positions
    * **View signers** assigned to the package, including their name, email, status, and whether they have recorded an e-signature
    * **Resend notifications** — queues a notification job to remind signers who have not yet completed their assignment
    * **Cancel the package** — sets the status to `cancelled` and optionally records a reason; this action is reversible only via the API

    <Warning>
      Cancelling a package prevents signers from completing it. Use resend to prompt signers instead whenever possible.
    </Warning>

    ## Filter by location

    If your account spans multiple locations, use the **Location filter** dropdown at the top of the signings list to narrow the view to a single location.
  </Tab>

  <Tab title="Signer: review and sign documents">
    ## Access your assigned packages

    <Steps>
      <Step title="Go to your packages">
        After signing in, navigate to **Signing → Packages** (or go directly to `/signing/packages`). You see a list of every signing package assigned to you.

        <Note>
          If you land on the onboarding walkthrough instead, complete or dismiss it. It's a two-step guide specific to the signer experience.
        </Note>
      </Step>

      <Step title="Open a package">
        Click any package in your list — or use a direct package link (`/signing/packages/:id`) shared by your manager — to open the detail view.

        The detail view shows all documents in the package and the current signing status for each one.
      </Step>

      <Step title="Review each document">
        Read through each document in the package. If you have questions, contact your manager before signing.
      </Step>

      <Step title="Sign">
        Click **Sign** on each document you are ready to complete. Safeclose records your e-signature with a UTC timestamp. If other signers are assigned to the same package, the package shows **complete** once everyone has signed.
      </Step>
    </Steps>

    ## Check co-signer status

    The package detail view shows all other signers on the same package — their names, status, and whether they have recorded an e-signature. You do not need to take any action for co-signers; monitoring is read-only.
  </Tab>
</Tabs>

## Package statuses

| Status      | Meaning                                                                |
| ----------- | ---------------------------------------------------------------------- |
| `draft`     | Created but not yet active; signers are not yet notified               |
| `active`    | Signers have been notified and can sign                                |
| `complete`  | All signers have recorded an e-signature                               |
| `cancelled` | The package was cancelled by a manager; no further signing is possible |

## API example

Fetch your signer queue programmatically to build custom integrations or dashboards.

<CodeGroup>
  ```bash Fetch signer queue theme={null}
  curl https://api.safeclose.com/v1/signing/signer/signings \
    -H "Authorization: Bearer <your-token>"
  ```

  ```json Response (200 OK) theme={null}
  {
    "signings": [
      {
        "id": "42",
        "status": "active",
        "location_id": "7",
        "e_sign_recorded_at": null,
        "full_name": "Jane Smith",
        "email": "jane@example.com"
      }
    ],
    "scope": "signer"
  }
  ```
</CodeGroup>

For manager-side endpoints (create, cancel, resend, document roster), see the [Signing API reference](/api/signing/manager-signings).

## Related topics

* [Signing packages concept](/concepts/signing-packages) — how packages, flows, and templates relate
* [Roles and permissions](/concepts/roles-permissions) — how signing access tiers control what you can do