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

# Access and permissions

> Who can do what in Devias. Every request from a person, API key, workflow, module or agent passes the same permission check in the server. Lists the three member roles, what an API key can do, and how workflows, modules and agents are limited.

Every request to the Devias server passes one permission check. What differs is **who is asking**: a person, an API key, a workflow, a module's server code or an agent.

## People

Each member of a workspace has one role.

| Role | Can |
| - | - |
| `owner` and `admin` | Everything: change the data model, manage members, modules, API keys, workflows and AI settings |
| `member` | Read and write records, documents and tasks, run workflows and module actions, and connect their own accounts |

An admin changes roles under **Settings → Members**.

## API keys

An API key is created under **Settings → API keys**, with an expiry chosen at creation. It carries its own list of permissions, such as "read and write records". A key created in the studio can read records; a key with more permissions is created through the API with a `permissions` map. A key is shown in full once, when it is created, and can be revoked at any time. Use a key for scripts and other services, and give it only what it needs. See [Authentication](https://docs.devias.io/reference/api/authentication.md).

## Workflows and modules

Workflows and a module's server code act as themselves, not as a person. They can read and write records and run actions. They can never manage the workspace.

## Agents

An agent acts with the role of the person who asked, and its tool list limits it further. It can never do more than that person could. History records both the agent and the person. See [Agents](https://docs.devias.io/concepts/agents.md).

## Related

* [Authentication](https://docs.devias.io/reference/api/authentication.md): sessions and API keys over HTTP.
* [Settings](https://docs.devias.io/guides/studio/settings.md): invite people, set roles, create API keys.
* [Tools and approvals](https://docs.devias.io/guides/agents/tools-and-approvals.md): limit what an agent may do.


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