Skip to main content

Workflow-Assigned Roles and Responsibilities

This article goes over the roles that can be assigned for Ironclad Workflows, as well as their permissions.

Use Case

Use this article to help decide what roles to assign different users in your Ironclad instance.

Permissions

Features

Workflows

Permissions

Ironclad Admin


Workflow Roles

Roles

Abilities

Create

Review

Sign

Archive

Workflow Owner

  • All roles here can be assigned to the Workflow Owner

  • Assignment defaults to the Workflow Creator (user who requests/submits the launch form), and can be re-assigned to any user in your Ironclad instance

X

X

X

X

Approver

(pre-defined in Workflow Designer)

  • Reviews and Approves the workflow, gating the workflow from moving to the Sign step

  • “Approval” is a catch-all action that can represent approval of purchase, deal, contract terms, latest draft, and/or specific properties

  • “Approval” can also act as a reminder for assigned users to complete specific actionsduring the Review step, e.g. “Vendor completed onboarding form”

  • Assignment is determined by conditions built in Workflow Designer

X

Approver (added in workflow)

  • Reviews and Approves the workflow, gating the workflow from moving to the Sign step

  • Manually assigned during the Review step when a new approver is added to the workflow

X

Signature Coordinator

  • Sends the signature packet to signers

  • Confirms signature packet recipients and edits recipient name or email, if required

  • Places signature tags on non-templated contracts

  • Uploads partially-signed or fully-signed documents

  • Assignment is determined by conditions built in Workflow Designer

X

Signer

  • “Signs” documents sent through e-Signature. “Accepts” documents sent through Click-to-Accept

  • Assignment is determined by conditions built in Workflow Designer

  • Workflows without a Signer assignment will skip the Sign step

X

Archiver

  • Confirms property data is accurate and complete before “Approving” and storing the record in Repository

  • Assignment is determined by conditions built in Workflow Designer

  • Workflows that auto-archive will skip the Archive step

X

Participant

  • All users with a role (e.g., Owner, Approver, Signer, etc.) or who were added via an @-mention comment.

Varies

Varies

Varies

Varies

Assignee

  • A user, or multiple users, who must complete a pending action in order to advance the workflow.

Varies

Varies

Varies

Varies


Update Workflow Role Assignments via the Public API

!

Release: One or more of the following features and functionalities will go live on July 23, 2026. To learn more about what's included in our July release, refer to What's New in Ironclad: July 2026.

You can reassign approvers, owners, and signers, on active workflows programmatically through the Public API. This update uses a paired endpoint to fetch eligible assignees before updating a role. Role reassignment honors Workflow Designer eligibility and workflow-state guardrails.


Resources

Explore articles, courses, and support options to get the most out of Ironclad.

Developer Docs

Support

Did this answer your question?