The advanced features that make vDocs a company platform

Turning one video into a clean guide is where most people meet vDocs. It's also where most people stop looking — and they miss the half that makes vDocs work at company scale. This post is that half: the advanced features teams grow into once documentation stops being a one-off and becomes something you run.

Steer the AI with prompt presets

Generation isn't a black box. A prompt preset is a saved, reusable set of instructions that tells the AI how to write a document — the persona it should adopt, the tone and depth, and even guidance for individual sections. Set one up once ("You are an expert operator writing for a first-day hire…"), and anyone on your team can pick it from the generation wizard instead of re-typing instructions every time.

Presets can be private to you or shared across your organization, so a team can standardize its documentation voice in one place. They're rolling out per document type — starting with Work Instruction, with more on the way.

Fork a doc for a different audience

Here's where presets get powerful. Fork takes an existing vDoc and rewrites it for a new audience — same structure, same screenshots, same key points, but the prose adapts to a different preset's tone and depth. Write one detailed guide for a new operator, then fork it into a concise expert reference in seconds. The steps and images stay locked; only the words change.

Add another language in one step

Documentation shouldn't stop at your head-office language. From any doc, Add Language regenerates it in another language — vDocs handles a wide range, from English, Spanish, Catalan and French to Chinese, Japanese and Korean, with many more available. Readers switch between the versions with a toggle right in the viewer, so one doc serves every market you operate in.

Export anywhere — including structured data

Your documentation shouldn't be trapped in one tool. Export any vDoc to PDF, Word, Markdown or HTML, with your own templates, branding, an optional cover page, and even the source video attached. Exports run through your organization's templates so everything that leaves the team looks like you.

There's also a structured export built for pipelines — a "Chunks" format designed to feed RAG systems and search. It's how your documentation becomes something machines can use, not just people. And this is the area we're investing in next: richer structured export for companies is coming soon, so your guides can flow straight into the internal tools and assistants your teams already rely on.

Share a vDoc with a link

Need to hand a guide to a client or a contractor? Share creates a public link that anyone can open without signing in — no account, no friction. You choose which language version to share, and the link stays live until you revoke it. Compiled projects can be shared the same way.

Scale it across your organization

vDocs is built for teams, not just individuals:

• Shared library and templates — reference materials and document templates every member can use.
• Branding — your logos and colors flow automatically into Word and PDF exports.
• Publish to organization — promote a personal doc to the shared org so everyone can access it, while your original stays yours; update or unpublish it any time.
• Roles and seats — admins manage members, invitations and seats centrally.
• Usage analytics — a shared credit pool with usage broken down by member.

Let your agents and pipelines use vDocs

vDocs isn't only a place you click — it's programmable, so your scripts, your CI pipelines and even other AI agents can drive it directly.

Create an API key in your profile and connect vDocs as an MCP server (the open standard for giving AI assistants tools). Point Claude, Cursor or any MCP-capable agent at it and it can generate a document from a recording, search and read your team's docs, and export them — on its own:

claude mcp add -t http -H "Authorization: Bearer YOUR_API_KEY" vdocs https://vdocs.ai/mcp

The same keys back a CLI and HTTP API — the surface for building agent skills and running vDocs in bulk. Generate, regenerate, translate and export documentation across an entire library programmatically, so the agents and automations your team builds can treat vDocs as a service, not a screen.

That's the difference between a tool you use and a platform you build on: the automations your team already runs can create and maintain documentation without a person in the loop.

The point

The basics turn a video into a guide. The advanced features turn vDocs into infrastructure: a consistent voice across every team via presets, one source that forks by audience and regenerates by language, export that feeds both people and pipelines, and an organization layer that keeps it all shared, on-brand and measured.

Want to put it to work in your company? Start free, or get in touch to talk about rolling vDocs out across your team.