# Workflow recipes: integrations working together

Source: https://versodocs.com/docs/recipes

Each recipe chains a few [integrations](https://versodocs.com/docs/integrations.md) around one review. Changes always come in as a draft or proposal, and nothing goes live until a person approves it.

Every integration has a short tour: in the app, open **Settings → Personal → Guides and tours**.

## Ops team on SharePoint or OneDrive

**For:** Operations teams whose SOPs live as Word files in SharePoint or OneDrive.

1. In **Settings → Integrations → Watch a folder**, link the SharePoint folder where people edit SOPs.
2. When someone saves a changed file, VersoDocs opens a proposal for its reviewers.
3. The **AI reviewer** from **workspace settings → AI reviewers** posts a summary and inline comments.
4. **Microsoft Teams** posts the review request as a card in the team channel.
5. A person approves, then the proposal is published as the new Current version.
6. **Cloud folders** writes the approved PDF or Word file, stamped with its version, to the folder people read.

**What changes for the team:** People keep editing files in SharePoint, and only reviewed versions reach the shared folder.

Docs and tours: [Watch a folder](https://versodocs.com/docs/cloud-folders.md#watch) ([tour](https://versodocs.com/docs/guides/integration-folder-watch)) · [AI reviewers](https://versodocs.com/docs/ai-reviewers.md) ([tour](https://versodocs.com/docs/guides/integration-ai-reviewers)) · [Microsoft Teams](https://versodocs.com/docs/teams.md) ([tour](https://versodocs.com/docs/guides/integration-teams)) · [Cloud folders](https://versodocs.com/docs/cloud-folders.md) ([tour](https://versodocs.com/docs/guides/integration-cloud-folders))

## Engineering on GitHub and Slack

**For:** Engineering teams who ship code against written specs.

1. Open a proposal on the spec and add the Jira or Linear issue under **Linked issues**.
2. **Slack** posts the review request in the channel you picked for the workspace.
3. Reviewers approve, then the proposal is published as the new Current version.
4. The **GitHub** check flags pull requests that still cite the old spec version.
5. The **GitHub** repo mirror rewrites the spec as Markdown in your repo.
6. **Jira** or **Linear** gets a comment on the linked issue saying the spec was published.

**What changes for the team:** Engineers build against the approved spec, and code review catches stale references before merge.

Docs and tours: [Jira](https://versodocs.com/docs/issue-links.md) ([tour](https://versodocs.com/docs/guides/integration-jira)) · [Linear](https://versodocs.com/docs/issue-links.md) ([tour](https://versodocs.com/docs/guides/integration-linear)) · [Slack](https://versodocs.com/docs/slack.md) ([tour](https://versodocs.com/docs/guides/integration-slack)) · [GitHub](https://versodocs.com/docs/github.md) ([tour](https://versodocs.com/docs/guides/integration-github))

## Writers in Word or Google Docs

**For:** Writers and reviewers who draft in Microsoft Word or Google Docs.

1. Install the **Microsoft Word** add-in or the **Google Docs** add-on and sign in.
2. In the add-in, search a document and open its approved version, or link the file you have.
3. Edit as usual, then click **Propose changes** to send your edits for review.
4. Reviewers comment and approve in VersoDocs, and a person publishes.
5. Everyone with the file open sees a notice when a newer approved version exists.

**What changes for the team:** Writers stay in their editor, and the team still has one reviewed, approved version.

Docs and tours: [Microsoft Word](https://versodocs.com/docs/word.md) ([tour](https://versodocs.com/docs/guides/integration-word-addin)) · [Google Docs add-on](https://versodocs.com/docs/google-docs.md) ([tour](https://versodocs.com/docs/guides/integration-google-docs-addon))

## AI agents that read and propose

**For:** Teams who use Claude, Cursor or Copilot alongside their specs.

1. Each member connects their agent in one click under **Personal settings → Your AI agents (MCP)**.
2. The agent reads only the Current version, or uses **Ask your docs** for answers with citations.
3. When something is out of date, the agent opens a proposal with its suggested edits.
4. The **AI reviewer** posts a first pass, then people review and approve.
5. A person publishes, and every agent reads the new Current version.

**What changes for the team:** Agents help draft and check, but every change is approved by people before it goes live.

Docs and tours: [Your AI agents (MCP)](https://versodocs.com/docs/mcp.md) ([tour](https://versodocs.com/docs/guides/developer)) · [AI assistants](https://versodocs.com/docs/ai-credits.md) ([tour](https://versodocs.com/docs/guides/integration-ai-assistants)) · [AI reviewers](https://versodocs.com/docs/ai-reviewers.md) ([tour](https://versodocs.com/docs/guides/integration-ai-reviewers))