Check fields a client cannot see while signing

How-to Last tested 25 October 2026

If a client cannot see changed wording during electronic signing, pause the signing request and have the authorized sender inspect the exact document, recipient and field settings. Check whether the value is absent, hidden, assigned to someone else or waiting on an earlier recipient. Visibility is a technical question; the responsible licensed professional decides whether the wording and any proposed change are authorized.

Capture the symptom before changing settings

Ask for a precise description: which document, which page, which field and which stage of the request? “I cannot see the updated delivery note” is more useful than “the signing app is broken.” Record whether the rest of the document is visible and whether the issue concerns text, an editable box or the invitation itself. Use a neutral example when describing the problem outside the authorized transaction team.

Keep real client information inside the approved workspace. Do not forward a signing link, request a password or collect a whole agreement merely to illustrate a missing field. A sender can record a document identifier and the affected area without placing the contents in a general-purpose support note. The file-permissions guide explains the separate question of who should see the material.

A real report illustrates why the distinction matters. In June 2025, a Docusign Community user said replacement price text was invisible during signing. An employee reply described a possible combination of multiple recipients, an assigned text field and no signing order, then pointed to order and prefill settings1. That is a reported configuration problem, not evidence that every missing field has that cause.

Confirm the intended document and recipient

Have the authorized sender compare the current request with the approved source document. Check identifiers, version labels and the field location, not only a familiar filename. Two files can share a title while containing different wording. If the approved version itself is uncertain, stop the technical diagnosis until the responsible professional identifies it; this page does not decide which version controls.

Next identify the recipient role that should read or complete the field. The sender, a buyer, a seller and a coordinator may have different tasks. Record the intended reader separately from the person allowed to edit. Refer questions about who may change a value or sign to the responsible licensed professional and the brokerage’s process before changing assignments.

Separate three controls

An invitation controls when a person enters the workflow. Visibility controls whether that person can see an item. Editing controls whether the person can change it. A read-only value may be visible; an assigned field may remain unavailable to another recipient. Do not use those terms interchangeably when recording what happened.

Adobe’s assignment instructions describe fields belonging to specific recipients, including optional fields left empty. They also distinguish an “Anyone” assignment from sender-prefill fields, and describe when entered content becomes locked to later editing2. These are provider-specific rules. Use the current instructions for the product and authoring mode in your own organization rather than transferring a setting name from a different service.

Check conditional behavior separately. Adobe’s current field-property reference describes conditions that can show, hide, enable or disable fields; a required field kept hidden or disabled does not need completing in that state3. An empty result can therefore have a different cause from incorrect ownership. Record the controlling choice and intended condition before changing either.

Walk through a fictional recipient model

The original example below uses only a fictional delivery note and buyer/seller role labels. Its rules are deliberately simple: a recipient must be invited; an unmet condition hides a field; a shared, owned or finished-owner value is visible; and only the unfinished owner can edit an unlocked field. Those are teaching rules we wrote, not a reconstruction of a provider’s implementation.

The six cases ran with the saved model and commands. The results preserve each input, expected result and actual result. Every case passed its declared expectation. That confirms only this small program’s behavior; it does not validate any real signing configuration.

Fictional caseInvitedVisibleEditable
Seller views unfinished buyer-owned fieldYesNoNo
Buyer views their own fieldYesYesYes
Seller views shared read-only valueYesYesNo
Seller waits behind the current buyerNoNoNo
Seller views finished buyer-owned valueYesYesNo
Buyer’s field has an unmet conditionYesNoNo

Start with the first two cases. The same value and document produce different results because the viewing role changes. In an authorized fictional draft, that suggests checking the assignment before assuming the document has lost its text. It does not authorize assigning the field to whoever happens to report the problem.

The third and fourth cases isolate different controls. Making a value shared and read-only changes visibility without granting editing. Moving a recipient later in a sequence prevents entry in this model, even for shared content. A sender needs to check both the reader’s place in the workflow and the intended access to the value.

The last two cases show why timing and conditions need separate notes. A value can become visible after an owner finishes, while a false condition can hide even the owner’s field. Seeing text in a completed file therefore does not prove that the intended person could read it at an earlier stage. Use an approved fictional draft to examine that earlier stage directly.

Verify a proposed correction before real use

Write down the intended outcome before changing a setting: for example, two recipients should be able to read the fictional delivery note, while only the authorized role can edit it. An outcome stated this way is easier to check than “make the field work.” Keep the model’s results separate from observations in the actual service.

Within an approved fictional test, inspect each recipient view and the relevant stage separately. Change one setting at a time, then record whether the intended view changed and whether another role gained unwanted editing access. Do not copy a client’s live signing link into the test or use real transaction documents as convenience fixtures. No provider test was performed for this article.

The authorized sender should also distinguish changing an unsent draft from modifying a request already in progress. If a proposed change touches approved wording, a signed document or the sequence required by the transaction, a licensed professional determines the appropriate action. A technical preview is not approval of the wording, the parties’ consent or the effect of a signature.

Close the loop with a clear handoff

Keep a short record of the symptom, the exact object checked, the intended roles and the technical result. Mark anything still uncertain. The recipient should receive a clear instruction from the authorized sender about which current request to use; this article does not tell a reader to continue with text they cannot inspect.

Retain the distinction when exporting the file. A completed PDF and a signing history may answer different questions about the workflow, as the export comparison shows. Neither substitutes for a decision about what the parties approved. Return unresolved technical behavior to the organization’s approved support route with fictional or appropriately minimized details.

Not covered on this page

Sources

  1. Docusign Community field-visibility report and employee reply. Report 2025-06-10; reply 2025-06-12. Opened 25 October 2026. ↩

  2. Adobe: assign form fields to recipients. Updated 2023-07-20. Opened 25 October 2026. ↩

  3. Adobe: form field properties. Updated 2026-09-09. Opened 25 October 2026. ↩

How we test: methodology. Found a mistake? Corrections.