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

# Settings

> What each page under Settings does in the Devias studio. Lists every Settings page by group (Account, Workspace, Data, Developer), and explains inviting members and roles, shaping the data model, and creating and revoking API keys.

**Settings** is at the bottom of the sidebar. Its pages are grouped by purpose.

## Settings pages

| Group | Page | Purpose |
| - | - | - |
| Account | Profile | The person's name and account details. |
| | Appearance | Light or dark theme, for this browser. |
| | Integrations | The person's own connections to services such as Google. |
| Workspace | General | The workspace's name, address and ID. The ID is what a script or the CLI asks for. |
| | Members | Invite people and set their roles. |
| | Modules | Install, update and connect modules. |
| | Navigation | Rename, hide and rearrange the sidebar. |
| | AI | Whether the assistant is set up, which model it uses, and how much has been used. |
| Data | Data model | Objects and fields. |
| | Views | The views of each object. |
| Developer | API keys | Keys for scripts and other services. |
| | Diagnostics | Details for debugging the studio's setup. |

## Invite members

1. Open **Settings → Members**.
2. Enter an email address, choose a role and invite. The person receives an invitation to join the workspace.

Roles are `member`, `admin` and `owner`. Only admins and owners can change roles. See [Access and permissions](https://docs.devias.io/concepts/access.md).

## Shape the data model

**Data model** adds objects and fields, including fields on an object a module shipped. A change takes effect at once in tables, forms, record pages, the API and what agents can see. See [Data model](https://docs.devias.io/concepts/data-model.md).

## Create an API key

1. Open **Settings → API keys** and create a key.
2. Choose when it expires.
3. Copy the key. It is shown once.

A key can be revoked here at any time. A key created in the studio can read records. A key with more permissions is created through the API with a `permissions` map. See [Authentication](https://docs.devias.io/reference/api/authentication.md).

## Related

* [Access and permissions](https://docs.devias.io/concepts/access.md): what each role can do.
* [Install and connect modules](https://docs.devias.io/guides/studio/modules.md): the Modules page.


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