---
title: Security
description: How Doss API access is controlled and how to manage your API keys safely.
sidebar:
  order: 5
---
The Doss API is built for server-to-server integrations that handle business-critical data.

## How access works

- **Admin control:** only enterprise admins can create and revoke keys, and every key's last use is visible on the Integrations page.
- **Read-only access:** the API can't create, change or delete data in Doss.
- **Organization isolation:** a key can only read data from the organization that created it.
- **Encryption in transit:** all requests use HTTPS with TLS 1.2 or later. Plain HTTP requests are rejected.
- **Key storage:** the full key is shown once, when it's created.

## Your responsibilities

An API key can read every table available to the API, regardless of any individual user's permissions in Doss. Manage keys the way you manage database credentials:

- Give keys only to the systems and people that need them.
- Store keys in a secrets manager, never in code, tickets, chat or shared documents.
- Use one key per integration and name it clearly, so you know what breaks if you revoke it.
- Rotate keys on a regular schedule and when someone with access leaves your team.
- Revoke unused keys. The Integrations page shows when each key was last used.
