Edit Prefilled values on the Webclient

Sparkify's Prefilled values feature lets you set documentation-field defaults once and have them auto-populate everywhere they apply. Edit is the action you reach on the Webclient project layer when you want to update the project-level prefilled value itself — open the existing prefill via a pencil icon, type the new value, and confirm. The new value is stored as the project-level prefill and becomes the default for every new Documentation created from the same template going forward.

Edit does not rewrite existing Documentations in the project. It only updates the prefill stored at the project layer. To also propagate the new value across Documentations that already exist in the project — i.e. to rewrite the field on each of them — an Owner or Manager has to run Apply as a separate step.

Who can use it

Edit on the Webclient is available to Owners, Managers, and Users. All three see the bolt icon and the Prefilled values button on the project info card, and find the Edit prefilled values option inside the dropdown. Only Guests are excluded. Edit is open to the User role because the action itself is low-stakes: it only updates the project-level prefill value; it doesn't rewrite existing Documentations. (That second step is Apply, which is restricted to Owners and Managers.) If you're a Guest and need a project-level prefilled value edited, ask an Owner, Manager, or User to run it.

Where Edit appears

Edit on the Webclient project layer is reached through the bolt icon in the top bar or the Prefilled values button on the project info card — both open the same dropdown with two options: Apply prefilled values and Edit prefilled values. The Workspace layer also has an Edit option that does the same thing at workspace scope: it updates the workspace-wide prefill value used as the default for new Documentations going forward. Neither Workspace-layer Edit nor project-layer Edit rewrites existing Documentations — that's Apply's job.

For the entry-point walkthroughs and screenshots, see the parent article: Prefilled values.

What Edit does

Edit lets you open the existing project-level prefill via a pencil icon and type a new value directly. Once you confirm, the new value is stored at the project layer and used as the default for every new Documentation created from the same template going forward. Existing Documentations in the project are not touched by an Edit; they keep whatever value they had when they were created.

The confirmation step

Edit's confirmation is a simple success notice. Once you've typed the new value and confirmed, you'll see a Prefilled value updated message — and that's it. No scope preview, no batch-rewrite, no propagation step. The new value is now the project-level prefill, used as the default for every new Documentation created from the same template.

If you also want existing Documentations in the project rewritten with the new value, that's a separate action: an Owner or Manager has to run Apply, which triggers the project-wide rewrite with its own scope-preview confirmation.

Edit or Apply?

Edit and Apply are two separate flows with different effects.

• Edit stores a new value as the project-level prefill. After you confirm, you get a "Prefilled value updated" confirmation — and that's it. New Documentations created from the template going forward start out with the new value, but existing Documentations in the project are not touched.
• Apply is what rewrites the value across every existing Documentation in the project that uses the chosen template. An Owner or Manager opens the Apply flow, picks the Documentation Template, picks the fields and the values, and confirms — at which point the project-wide rewrite happens.

Edit and Apply are different flows. Editing the Prefilled values on the project level and Applying the prefilled values are independent steps. If you only need to change the default going forward, Edit is enough; to also rewrite existing Documentations, ask an Owner or Manager to run Apply (Users can run Edit but not Apply).

Edit vs Apply: which step is the high-stakes one?

Edit alone is low-stakes — it only updates the project-level prefilled value used as the default for new Documentations going forward. Existing Documentations are untouched, so an edit mistake is easy to roll back: just open Edit again and type the previous value.

The high-stakes step is Apply, which rewrites the same field across every existing Documentation in the project that uses the chosen template. Apply has no undo button — once an Apply confirmation is written, the only way back is to run Apply again with the previous value. If you (as an Owner or Manager) plan to chain an Edit with an Apply, the moment to catch a typo is on Apply's scope-preview confirmation, not after.