Managing due dates and expiration controls
3 min read
Updated Apr 11, 2026
Due dates and expirations are different controls. A due date communicates expected completion timing, while link expiration determines how long the access path remains valid.
Before you begin
A package in the review step or active sender-side management
A real completion deadline if one exists
Awareness of workspace expiration warnings
Set the due date intentionally
Use the due date when recipients should understand a real deadline.
That due date should align with reminder cadence and the message you send alongside the package.
Choose link expiration separately
Link expiration determines when the recipient access path stops working.
You can keep the due date and link expiration aligned, or use a shorter access window for more sensitive workflows.
Use warnings and follow-up together
Workspace defaults can warn about upcoming expiration and control reminder behavior.
Check status and activity before changing the package or sending more follow-up.
Pro Tips
Avoid due dates that feel arbitrary to recipients.
If a document must expire quickly, mention that explicitly in the message.
Review expiration defaults during workspace setup so every sender starts from the same baseline.
Was this article helpful?
Use this as a quick signal while the public knowledge base is static.