diff --git a/docs.json b/docs.json
index d60812f..3c95431 100644
--- a/docs.json
+++ b/docs.json
@@ -76,6 +76,7 @@
               "platform/metrics-export",
               "platform/activity-logs",
               "platform/secrets",
+              "platform/machine-accounts",
               "platform/locations"
             ]
           },
diff --git a/platform/machine-accounts.mdx b/platform/machine-accounts.mdx
new file mode 100644
index 0000000..b292b5a
--- /dev/null
+++ b/platform/machine-accounts.mdx
@@ -0,0 +1,130 @@
+---
+title: "Machine Accounts"
+description: "Create non-human identities for applications, CI/CD pipelines, and services to authenticate with Datum APIs"
+---
+
+Machine accounts give non-human workloads — CI/CD pipelines, backend services, and scripts — a stable cryptographic identity to call Datum APIs. They authenticate using RSA key pairs rather than shared passwords or long-lived user tokens.
+
+## When to use machine accounts
+
+| Use case | Example |
+|----------|---------|
+| CI/CD pipelines | GitHub Actions deploying resources on every merge |
+| Kubernetes workloads | A pod calling the Datum API using a projected secret |
+| Backend services | A service authenticating as itself, not as a user |
+| Local automation | Scripts that run without a browser-based login |
+
+## Create a machine account
+
+1. Open your project in the [Datum Cloud portal](https://cloud.datum.net).
+2. Navigate to **Machine Accounts** in the left sidebar.
+3. Click **Create machine account**.
+4. Enter a lowercase name (e.g. `ci-deploy`) and an optional display name.
+5. Choose a key type:
+   - **Datum-managed** — Datum generates an RSA key pair. The private key is shown **once** at creation time. Download it as a JSON credentials file before closing the wizard.
+   - **User-managed** — You provide your own RSA public key in PEM format. Datum stores only the public key and never sees your private key.
+6. Click **Create**. Once the account's identity email is provisioned, your credentials are ready.
+
+<Note>
+  For datum-managed keys, the private key is only displayed once. Download the credentials file before closing the wizard — it cannot be recovered later.
+</Note>
+
+## Manage keys
+
+Open a machine account and navigate to the **Keys** tab to add or revoke keys.
+
+- **Add a key** — create an additional datum-managed or user-managed key at any time.
+- **Revoke a key** — immediately invalidates the key. Any tokens issued with it will stop working at expiry.
+
+To rotate keys with zero downtime: add the new key, update your workloads to use it, then revoke the old key.
+
+## Assign roles
+
+Machine accounts are IAM principals like any other member. Assign roles from the **Policy Bindings** tab on the account's detail page, or from **Settings → Members** in your project or organization.
+
+## Disable or delete an account
+
+- **Disable** — suspends authentication without removing the account or its keys. Re-enable at any time from the **Overview** tab.
+- **Delete** — permanently removes the account and revokes all associated keys. This cannot be undone.
+
+## Using credentials
+
+After creating a machine account, you'll have a credentials file to use for authentication.
+
+### Credentials file format
+
+When you create a datum-managed key, Datum returns a JSON credentials file:
+
+```json
+{
+  "type": "datum_machine_account",
+  "client_id": "...",
+  "private_key_id": "...",
+  "private_key": "-----BEGIN RSA PRIVATE KEY-----\n...",
+  "client_email": "my-account@my-namespace.my-project.iam.datum.net"
+}
+```
+
+Treat this file like a password — store it in a secrets manager and never commit it to source control.
+
+### datumctl
+
+```text
+datumctl auth login --credentials-file /path/to/credentials.json
+```
+
+Or set the environment variable so all subsequent commands pick it up automatically:
+
+```text
+export DATUM_CREDENTIALS_FILE=/path/to/credentials.json
+datumctl organizations list
+```
+
+### GitHub Actions
+
+Store the contents of the credentials file as a repository or organization secret (e.g. `DATUM_CREDENTIALS`), then write it to disk in your workflow:
+
+```yaml
+- name: Authenticate with Datum
+  run: echo "$DATUM_CREDENTIALS" > /tmp/datum-credentials.json
+  env:
+    DATUM_CREDENTIALS: ${{ secrets.DATUM_CREDENTIALS }}
+
+- name: Run datumctl
+  run: datumctl organizations list
+  env:
+    DATUM_CREDENTIALS_FILE: /tmp/datum-credentials.json
+```
+
+### Kubernetes
+
+Create a Kubernetes secret from the credentials file:
+
+```text
+kubectl create secret generic datum-credentials \
+  --from-file=credentials.json=/path/to/credentials.json
+```
+
+Mount it into your pod and point the environment variable at it:
+
+```yaml
+env:
+  - name: DATUM_CREDENTIALS_FILE
+    value: /var/secrets/datum/credentials.json
+volumeMounts:
+  - name: datum-credentials
+    mountPath: /var/secrets/datum
+    readOnly: true
+volumes:
+  - name: datum-credentials
+    secret:
+      secretName: datum-credentials
+```
+
+### Environment variable
+
+Any tool or SDK that respects `DATUM_CREDENTIALS_FILE` will authenticate automatically when the variable is set:
+
+```text
+export DATUM_CREDENTIALS_FILE=/path/to/credentials.json
+```