> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devias.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The docs are served at https://docs.devias.io. Every path in these docs is relative to that root: /llms.txt is https://docs.devias.io/llms.txt.
> Devias is an open-source platform that works as an operating system for a business: a core (records, views, workflows, agents, permissions) with installable modules.
> Pages are typed by folder. concepts/ explains what things are, guides/ gives procedures, reference/ is exhaustive (SDK, CLI, HTTP API), operate/ covers hosting. Use /start/glossary for exact terms.
> Every id in a module (module, object, field, view, action, workflow, step, connection, variable, event, policy) is a uuid. Generate them with `devias id <count>`. Never invent dotted or readable ids.
> Run `devias plan` and read its output before `devias apply`. Apply only what the plan says.
> The OpenAPI document, including the routes of the modules in the reference setup, is at /reference/api/openapi.json.
> Devias is young and changes quickly. If a page and the source repository (github.com/devias-io/devias) disagree, the repository is right.

# Modules

> What a Devias module is, which modules are core, how installing works with a plan you review before applying, and how ids keep a module's data separate from a workspace's own data.

A **module** is a package that adds one area of the business to a workspace. It can contain objects and fields, views and layouts, navigation, commands, actions, workflows, connections, variables, events, agents, skills and optionally server code. The CRM is a module. So are quotes, invoicing, expenses, products and inventory. A module can also connect to an outside service: Stripe takes payments, Resend sends email and Context.dev enriches people.

## Core and installable modules

A **core** module comes with every workspace. The studio itself is one: Home, Tasks, Documents, Workflows, Agents and Skills. Every other module is installed on request from **Settings → Modules**.

## Install with a plan

Installing a module is a two-step operation.

1. Devias computes a **plan**: what the module would add or change in this workspace. Nothing is written.
2. After review, the plan is **applied**.

Uninstalling removes what the module owns and nothing else. The same two steps exist on the command line as `devias plan` and `devias apply`. See [Plan and apply](https://docs.devias.io/guides/modules/plan-and-apply.md).

## Ids and ownership

Everything a module declares has an **id**, which is a uuid that never changes. Names and labels can change between versions and ids stay the same. Nothing reads meaning out of an id.

Ids define ownership. A module owns what it declared. The workspace owns what people created. An update to a module therefore never touches a workspace's own data. Generate ids for a new module with `devias id <count>`; see [`devias id`](https://docs.devias.io/reference/cli/id).

## Related

* [Install and connect modules](https://docs.devias.io/guides/studio/modules.md): use modules in the studio.
* [What a module is](https://docs.devias.io/guides/modules/what-a-module-is.md): build one.
* [Built-in modules](https://docs.devias.io/guides/modules/built-in-modules.md): the modules that ship with Devias.
* [Glossary](https://docs.devias.io/start/glossary.md#id): definition of id.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.