Documentation

VentionDesk is the cockpit for freelancers and agencies: customer projects with tasks, tickets with response deadlines, customers, invoices, time tracking and documents in one place — and Claude as a team member who pulls tasks through an interface and reports back.

This documentation describes what the application can do today. The values in it — prices, deadlines, reminder levels, scopes, provider guides and the API endpoints — come from the same code as the application itself.

Where to start

• New here? Getting started takes you from sign-up to your first invoice.
• Day to day: The user guide walks through the interface area by area — overview, projects, tasks, tickets, customers, finances, documents, statistics, time tracking, workspace and settings.
• Connecting services: Integrations explains step by step how to connect GitHub, hosting providers, email services, error trackers and Stripe.
• Tickets from your own sites: The ticket intake accepts reports from contact forms, apps and servers.
• AI apps: Connect Claude, ChatGPT, Cursor or Codex with your own sign-in — Connect AI apps.
• For developers: API basics, the API reference, Claude and MCP and the webhooks.

Roles

In the cockpit, VentionDesk has two roles: the owner and staff members. The owner sees everything. Staff members see projects, tasks, tickets, customers, documents and time tracking — but no finances, no statistics, no hourly rates and budgets and no access settings. The server enforces this boundary, not just the interface.

There are also API keys: agent keys for Claude or your own automations, and intake keys for the ticket intake. How they work is explained under API basics.

Help

Questions these pages don’t answer are answered by support at support@ventiondesk.com (opens in a new tab).