---
title: Collaboration
description: "Reviews, approval gates, scheduled publishing, style linting, glossary, and access control for docs teams."
---

# Collaboration

The dashboard includes a full editorial workflow so docs changes ship with the same rigor as code. Everything below lives under your project in the [dashboard](https://syntext.dev) and is also available via the [Collaboration API](/api-reference/collaboration/overview).

## Reviews

Request review on changed pages before they publish. Reviewers see a diff, can comment, and approve or request changes — like a lightweight PR flow for docs edited in the [web editor](/platform/web-editor).

<Note>
If your docs live in a git repo, use normal PRs — Syntext builds a [preview](/api-reference/webhooks/overview) for every PR automatically. Reviews are for content managed in the web editor.
</Note>

## Approval Gates

Require sign-off from specific people before certain paths can publish:

- Define a gate with a **path pattern** (e.g. `api-reference/**`, `pricing`) and **required approvers**
- Publishes touching gated paths are held until approved
- Rejections include a reason and notify the author

Use gates for legally sensitive pages, pricing, and security documentation.

## Scheduled Publishing

Stage content now, publish it later — e.g. docs for a feature that launches Tuesday 9am:

1. Save the content (it stays unpublished)
2. Create a schedule with the go-live time
3. Syntext publishes and rebuilds automatically at that time

Schedules can be canceled any time before they fire.

## Preview Links

Create shareable links to unpublished content for external reviewers — optionally password-protected and expiring. No Syntext account required to view.

## Style Linter & Rules

Enforce a consistent voice across all writers:

- **Built-in rules** — broken links, missing descriptions, heading structure
- **Custom style rules** — terminology ("use *sign in*, not *login*"), banned phrases, tone
- **Auto-fix** — mechanical violations can be fixed in one click
- Runs in the editor as you type, and on demand via `POST /lint`

Pair with [`stx check`](/cli/check) to enforce the same rules in CI.

## Glossary

Define canonical terms once:

- Terms get **hover definitions** on the deployed doc site
- The linter flags inconsistent usage of glossary terms
- Manage in the dashboard or via the [API](/api-reference/collaboration/overview)

## Content Ownership

Assign owners to path patterns (`guides/** → @sarah`). Owners are notified when their pages go stale (90+ days without updates) or receive negative feedback — no more orphaned docs.

## Access Control

For docs that shouldn't be fully public:

- **Access rules** — restrict path patterns to audiences or authenticated users
- **IP allowlists** — restrict access to office/VPN ranges
- **Access logs** — audit who accessed gated content
- **Access check API** — test rules before rolling them out

For tiered content (e.g. partner-only pages), see [Audience Gating](/guides/audience-gating).