Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteUse Sanity Studio’s draft, preview, review, and publishing capabilities to keep career content off the live site until it has been checked and an authorized user publishes it. “Sanity Workflows” is not a single, universally configured feature: available approval actions, previews, roles, and release tools depend on how your project is set up.
What “Sanity Workflows” means in practice
Sanity Studio can support a review process through drafts, publishing controls, previews, roles, and custom document actions. Your team may have added approval steps, but there is no guarantee that every Studio has the same review buttons or approval states. Sanity’s Content operators quick start guide says custom actions may be added by the development team; ask your Studio maintainer which actions are available.
As an Amazon Associate I earn from qualifying purchases.
Sanity Docs describes previewing changes in a secure, high-fidelity setting before publication as essential to a smooth editorial process. That preview is useful only if your project has configured it and connected it to the intended page.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Review and publish career content step by step
- Open or create the document in Sanity Studio. New content starts as a draft, visible to the team in Studio rather than to site visitors. Editing an already published document creates an unpublished draft copy, so changes do not become live until publication.
- Complete the fields your project requires. Required fields depend on the project’s schema and are marked in the interface. Do not assume there are career-specific fields or mandatory SEO checks unless your project has configured them.
- Preview the draft in context, if available. If your team has configured Presentation Tool or another preview integration, inspect how the content appears on its intended page. The Presentation Tool can display a live preview beside Studio and update as the draft changes; setup and implementation vary by project.
- Follow your team’s review process. Use the approval steps and document actions available in your Studio. Agree who checks career claims, tone, links, and any sensitive or regulated material under your own editorial policy; Sanity’s general product documentation does not set those standards.
- Have an authorized user publish. Confirm that the person publishing has the required access. A Contributor role can edit drafts but cannot publish, according to Sanity’s roles guide. Check the user’s full set of roles because permissions can accumulate.
- Check the live page. After publication, inspect the page through your site’s normal quality-assurance process. Sanity distinguishes draft content from published content; ensure the public experience presents the published version.
Choose the right level of workflow control
A straightforward draft-review-publish process may be enough when one item is reviewed and published individually. A more customized setup may be appropriate when several items must launch together, reviewers need in-context previews, or approval needs to be enforced through permissions rather than team convention.
#1 Best Overall
- Team convention: A documented handoff can organize review, but it does not by itself prevent someone with publish access from publishing.
- Custom document actions: Developers can add approval steps or other actions. Sanity’s document-actions workflow demo describes a visual workflow, but notes that the demo does not have a formal security model. Do not treat a displayed workflow state as an access-control boundary unless permissions are implemented and verified.
- Role-based separation: Assign draft editing and publishing appropriately. For custom access rules, Sanity’s Access API guide describes custom role configuration. Its documentation marks custom roles as an Enterprise feature. Restrictive rules may also need permissions for system documents used by drafts, versions, and releases, not just the career-content document types.
- Coordinated launches: Content Releases group document updates for coordinated publication. Sanity’s release-flow documentation says Content Releases are available on certain Enterprise plans, while Scheduled Drafts are available on Growth or above. Verify current plan entitlements and project configuration before designing a process around either feature.
What to confirm with your Studio maintainer
- Which document actions or approval steps are available, and who is expected to use each one.
- Whether a working preview is configured for the career-content page and shows the draft rather than only the published version.
- Which roles can edit drafts and publish, including the combined effect of a user’s assigned roles.
- Whether the team needs individual scheduled publishing or coordinated releases, and whether the project’s plan includes the relevant feature.
- Whether custom permissions cover the system documents needed for drafts, versions, or releases.
Custom actions, preview integrations, and access controls can require development work. Base decisions on what is actually configured in your Studio, not on a generic set of assumed workflow buttons.
Quick Recap
Rank #3
Rank #2
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
