Signature enrollment and replacement¶
Signature enrollment stores the image that supported WorkOS approval and signing flows can use for a person's workspace staff record. Replacing that image changes the reusable asset. It does not, by itself, sign a document, approve work or grant signing authority.
Local documentation draft. Figma defines the intended file-and-PIN journey. The current frontend displays sample controls and success states without uploading or saving a signature. Backend storage and authorization constraints remain open; deployment and audience acceptance are unverified.
What you maintain¶
The account signature is an image uploaded for the selected staff record. The intended page accepts JPG or PNG and requires an existing authorization PIN. The service processes the image for later use in supported tasks.
This page does not provide a drawing pad, editable legal-name/title/disclaimer form, saved-image preview, history list, delete action or undo operation in the inspected contract. Such fields in old sample data do not establish supported account actions.
| Activity | What it establishes |
|---|---|
| Choose a file | A proposed upload, once the frontend is connected |
| Save with the authorization PIN | A request to store or replace the staff signature image |
| Check enrollment | Whether the staff record has a nonempty signature reference |
| Open a signing task | That task's separate eligibility, document and signing requirements |
| Complete signing or approval | The outcome recorded by the corresponding work process |
Ownership and business meaning¶
Maintain your own signature in the intended workspace. Do not use another person's PIN or image. A manager's responsibility for work does not automatically authorize changing a colleague's signature.
For managers and executives, enrollment is a preparation step. A rollout should verify that the right people can enroll an image, recover from failures and complete the particular signing tasks their roles permit. A stored image or enrollment flag is not evidence of approval, signer identity validation for every use, a legal certification or an enforceable agreement.
The account password and authorization PIN remain separate credentials. Changing the image does not change either credential or end existing sessions. Replacing it must not be assumed to rewrite documents that were already signed or to remove images already incorporated into saved outputs.
Continue with the right guide¶
Use enroll or replace your signature for the intended account steps and troubleshooting. Then return to the document signing task or other authorized process that needs it. Private engineering documentation records current authority, persistence and recovery constraints.