Controlled renaming improves clarity for signers, reduces misrouting and helps maintain consistent records across cloud storage and audit logs without altering document content or signature validity.
An HR Manager often sends offer letters and onboarding forms using signing links. They need the ability to rename files to include candidate names and roles for recipient clarity while ensuring the audit trail records the change and the signed document remains legally valid.
A Compliance Officer reviews naming controls and retention rules. They require configurable permissions so renaming is limited to authorized users and all modifications are timestamped and recorded to meet audit and regulatory requirements.
Organizations that manage high volumes of signatures and decentralized signers often require safe in-link renaming to help recipients identify documents correctly.
Proper role-based controls and audit logging let these teams enable renaming while preserving compliance and record integrity.
Fine-grained settings to allow or block visible filename edits for recipients and senders. Controls should include role-based restrictions and the option to lock filenames while still permitting field-level edits inside the document.
Complete logging of filename changes, including user identity, timestamp, and prior names. This audit information must be retained alongside signature events to maintain a clear chain of custody for legal and compliance reviews.
Configurable synchronization between the signing platform and cloud storage to control whether visible renames propagate to connected drives. Administrators can choose to update stored filenames or preserve originals depending on retention policies.
Administrative controls that assign renaming privileges only to authorized roles, ensuring that only trusted users can change titles and that those actions are subject to review and retention rules.
| Workflow Setting Name and Configuration | Value |
|---|---|
| Rename permission scope for signing links | Authorized only |
| Audit logging level for filename changes | Full detail |
| Cloud sync behavior after rename | Update optional |
| Retention policy alignment for renamed files | Preserve originals |
| Notification settings on filename edits | Send alerts |
A recruiter sends an offer through a signing link with a generic file name
Resulting in faster signer recognition and fewer returned or misfiled documents.
A school administrator distributes permission slips by signing link to multiple guardians
Ensures records are correctly matched to student files and simplifies later retrieval.
| Feature Availability and Technical Details Overview | signNow (Recommended) | DocuSign | Adobe Sign |
|---|---|---|---|
| Rename via signing link supported | |||
| Audit trail records filename edits | |||
| Permission controls for rename operations | Granular roles | Limited roles | Granular roles |
| Cloud sync control for renamed files | Selective sync | Overwrite | Selective sync |
Si vous avez besoin de personnaliser le nom de votre document lors du partage via un lien de signature, vous pouvez le faire sans renommer le modèle de document existant. Tout ce que vous avez à faire est de modifier le lien de signature lui-même.
Accédez à votre dossier Modèles dans airSlate SignNow, sélectionnez le modèle que vous souhaitez partager, et cliquez sur Créer un lien d'invitation.
Votre lien de signature apparaît dans la fenêtre contextuelle. Copiez l'URL et collez-la où vous pouvez apporter des modifications avant de partager le lien avec un signataire.
Ajoutez le fragment suivant à la fin de votre lien de signature : “?sgn_doc_name=” (aucun espace ni guillemets requis). Ensuite, tapez le nouveau nom du document après “=”.
?sgn_doc_name=John_Smith_Candidature
Une fois que votre destinataire suit le lien de signature modifié, le document s'ouvrira et portera le nom que vous avez défini.
Note : Vous pouvez demander à votre département informatique de configurer une fusion de courrier pour cette fonctionnalité.
