Adding approvers and CC recipients
3 min read
Updated Apr 13, 2026
Not every participant should be a signer. Approver and CC roles help you separate required action from simple visibility, which keeps routing cleaner and audit records easier to interpret.
Before you begin
A draft with the core signer list
Clarity on who approves versus who only needs a copy
A routing plan if approvals must happen before signatures
Use approvers for required review
Approvers belong in the flow when a person must actively review or approve before the workflow should be treated as complete.
Pair this with sequential routing if the approval should happen before downstream signers act.
Use CC for visibility only
CC recipients are useful for stakeholders who need the record but should not change timing or action requirements.
Too many CCs can create noise, so keep them limited to people with a real need to know.
Review the experience from the recipient side
Before sending, think about what each participant expects to see and when.
Clean role assignment makes recipient messaging and follow-up much easier.
Pro Tips
If a stakeholder might delay the workflow, make them an approver instead of a CC.
Document who owns approval decisions before you send the first package in a new process.
Keep recipient roles stable across repeated workflows so audit evidence reads cleanly.
Was this article helpful?
Use this as a quick signal while the public knowledge base is static.