Actions: the core unit of work
What an Action is, its types, and why everything you do flows through Actions.
Actions are the work
In Velsano the Action is *the* work object. A risk to mitigate, a renewal to run, a lifecycle motion to drive, an expansion to chase, a plan objective to hit — each is an Action, with a type, an owner, a due date, a priority, a set of tasks, and a lifecycle status.
Why one object for everything
Because it means all your work — what you create and what the AI proposes — lands in one queue, reports the same way, and closes the same way. Tasks always live under an Action, so nothing escapes the work model or your reporting.
The types
An Action's type captures *why* the work exists:
- Risk — something threatening the account.
- Lifecycle — an onboarding or adoption motion.
- Renewal — running a renewal.
- Expansion — an upsell or cross-sell.
- Activity — general follow-up work.
- Objective — a success-plan objective (created from a plan, not the normal Action picker).
Descriptions and comments support rich text. Types can be tailored per tenant.
Related: *Creating and assigning Actions* · *The work-item drawer* · *Today: your AI-prioritized home*