Enroll or replace your signature¶
Draft intended journey based on WorkOS 06 Final Screens and inspected code. The current frontend's Choose File control is unconnected and Save Signature navigates to a sample success state. It does not perform the upload or save. A connected environment and reader walkthrough remain unverified.
Use this page to maintain the reusable signature image for your own staff record in the selected workspace. Actual approval and document signing are separate tasks.
Before you begin¶
You need access to WorkOS in the intended workspace, your own staff record, a suitable signature image and a configured authorization PIN. A PIN is required even for your first signature upload.
Check the displayed person and workspace. If either is wrong, stop and return through normal workspace selection or contact support. Do not try changing another person's signature or copying a different staff identifier into an address.
Prepare a clear image of the signature you intend to use. Keep the original safely so you can provide it again if needed. The intended format is JPG or PNG; avoid uploading unrelated documents or other people's information.
Open the signature page¶
- Open My account in WorkOS.
- Select Signature beside Profile and Authorization PIN.
- Review the identity and the Approval Signature explanation.
- Find Choose Signature File, Confirm with Authorization PIN and Save Signature.
The screen's No file selected yet describes the proposed upload. It is not a live statement that no signature is stored. The current account page does not show a saved-image preview or a signature history.
An Active or Approver badge in the current sample frontend is not evidence of your actual role or enrollment. Resolve identity or access questions before entering a PIN in a connected flow.
Choose the image¶
- Under Choose Signature File, select Choose File.
- In the connected implementation, choose your JPG or PNG image.
- Check that the selected image is the one you intend to store.
- Continue only when the connected application has accepted the selection.
The current frontend has not wired this control to a file picker or submission. If nothing happens there, it is not evidence that your file was rejected.
The uploaded file is checked for its actual image format; renaming a file to end in .jpg or .png does not convert it. The stored image is fitted within 500 by 500 pixels and converted to JPEG. Do not rely on the original dimensions, file format or transparency being retained exactly. Use an image that remains legible when reduced.
No reader-facing maximum file size is established by the inspected account screen. Environment request limits and workspace storage limits may still reject an upload. If a size or format message appears in a connected version, record it and follow the stated correction instead of repeatedly uploading a larger file.
Confirm and save¶
- In Confirm with Authorization PIN, enter your authorization PIN for this workspace.
- Review the selected image and account.
- Select Save Signature once.
- Wait for the connected service result before leaving or trying again.
If you have not set a PIN, use Authorization PIN, complete its setup and return. The temporary code used during PIN setup is not the PIN to enter here.
Use Discard before submitting if you do not want to continue with the proposed selection. Discard is not an undo operation for a completed save. The current frontend implements it as navigation back to the default page.
A successful save makes the uploaded image the staff record's reusable signature. It does not approve an outstanding request or finish a signing task. Return to the original task and review its own requirements.
Replace an existing signature¶
Use the same image-and-PIN sequence. A new upload replaces the stored image at its existing storage location; the account page does not expose an older-version selector or automatic restore.
Keep the intended replacement available until the result is clear. Do not assume an error means the old image is untouched: the storage write can finish before a later save or accounting step fails. If the result is uncertain, contact support before repeated replacements.
Replacing the reusable asset is not a supported way to alter a previously signed document. Existing documents, signing records and any signature image already embedded in them follow their own lifecycle.
Understand enrollment and signing readiness¶
A system enrollment check asks whether your current staff record has a signature reference. It does not return the image, prove it can currently be downloaded or establish that it matches the image you just selected.
A signing task also checks the work assignment, document, allowed action and other conditions. If it still says enrollment is missing after a connected save, return to that task to refresh its checks. If the message persists, report the workspace and task to support. Do not approve or sign unrelated work simply to test the image.
The inspected account flow records a signature-update activity request. It does not establish a separate signature-change email or a visible account history list. The frontend's sample Signature saved message is not a service receipt.
If an assistant directed you into secure setup, keep the image and PIN in that account surface. Return through the supported journey after saving. Enrollment alone does not establish that a separate assistant action or document-signing operation succeeded.
When workspace access changes¶
A valid PIN and signature image do not override workspace access restrictions. If the workspace becomes unavailable, ask the organization administrator to distinguish product assignment or subscription access from an administrative pause. Replacing your image or resetting a working PIN does not resolve those restrictions.
If the connection closes after Save Signature, the image may already have been processed or stored. Keep the original attempt details and seek support before submitting another replacement. Restoring workspace access alone does not confirm the saved image or complete the original signing task.
Recover from a problem¶
| Symptom | What to do |
|---|---|
| Choose File does nothing | In the current WIP frontend the control is unconnected; confirm that the environment has a working upload journey |
| The image is rejected | Use a genuine JPG or PNG image. Record the exact message if a valid PNG is described as unsupported |
| PIN is missing or rejected | Complete PIN setup or replacement for this workspace; do not use the temporary email code |
| Storage limit prevents the upload | Ask the organization administrator to review capacity and any stated recovery option |
| Save failed after processing began | Treat the outcome as uncertain; contact support before another replacement |
| Signature saved appears after navigation | The current frontend uses a sample state; this does not prove any change |
| Signing still reports missing or unusable enrollment | Refresh the original task and seek support if the mismatch remains |
| You need to restore an older image | There is no account-page undo/history action; retain your source image and seek an authorized recovery path |
Workspace capacity checks can consider the incoming image before replacement is complete. Do not assume that replacing an existing signature must pass because the final image might be smaller.
Getting help and reader responsibilities¶
Users: provide only your own image and PIN through a connected account surface. Keep the original image available and avoid repeated saves when the outcome is unclear.
Managers and executives: treat enrollment, readiness and completed signing as different milestones. Confirm operational recovery and role access during rollout; do not infer legal or security guarantees from a reusable image.
Organization administrators: resolve membership, staff identity and capacity through authorized processes. The current sample claim that an administrator can “unlock signature changes” does not establish an implemented unlock feature.
Platform staff and support: ask for the workspace, time, failed stage, visible message and relevant task/support reference. Do not request the PIN or a signature image in an ordinary support ticket. Use an approved secure process if inspecting an asset is necessary.
Engineering, design and operations teams: verify current-user targeting, image validation, storage/database outcomes, recovery, enrollment reads and protected return. Exact limitations belong in the private reference. All nine audience reviews remain pending.