> ## 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.

# Install and connect modules

> How to manage modules under Settings → Modules. Covers installing a module from a reviewed plan, updating and uninstalling, workspace and personal connections to outside services, and the Events and Workflows tabs of a module that receives events.

Modules add whole areas to a workspace. They are managed under **Settings → Modules**. A module's page says what it adds, and has tabs for installing, connections, events and workflows where they apply.

## Install a module

1. Open **Settings → Modules** and choose a module from the list.
2. Open the **Install** tab. It lists exactly what would be created, and anything the module says needs review. Nothing is written yet.
3. Press **Install** and confirm. The module's objects, views and pages appear in the sidebar.

## Update or remove a module

* When a newer version exists, the module's page offers **Review changes**, which shows what would change before it is applied.
* **Uninstall** removes everything the module owns and never touches what people created themselves.
* Core parts of the studio cannot be uninstalled.

## Connect a module to an outside service

A module that needs a connection has a **Connections** tab. Some modules talk to services such as Stripe or Resend.

| Kind | Belongs to | Set up by |
| - | - | - |
| Workspace connection | Everyone in the workspace, such as a Stripe API key | An admin |
| Personal connection | One person, such as their own Google account | Each person, under **Settings → Integrations** |

Secrets such as API keys are stored encrypted and afterwards shown only as a masked hint.

## Events and workflows of a module

* If a module receives events from a service, its **Events** tab shows the address to give that service and the events received so far.
* A module can ship workflows that react to those events. They are on the module's **Workflows** tab with how each one last went, and in the Workflows list marked with the module's name. They can be switched on or off. To change one, make a copy. See [Workflows in the studio](https://docs.devias.io/guides/studio/workflows.md#workflows-that-ship-with-a-module).

## Related

* [Modules](https://docs.devias.io/concepts/modules.md): what a module is and how ids keep modules apart.
* [What a module is](https://docs.devias.io/guides/modules/what-a-module-is.md): build one.
* [Connections and events in a module](https://docs.devias.io/guides/modules/connections-and-events.md): declare them.


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