# Couchbase Capella temporary access

[Temporary access overview](/docs/concepts/temporary-access) covers target setup, connection methods, and credential handling.

Couchbase targets provision Capella database credentials through its v4
management API. The encrypted management credential is a Capella API token
with Project Owner or Organization Owner access.

```json
{"provider":"couchbase","executor":"in_do","organizationId":"aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa","projectId":"bbbbbbbb-bbbb-4bbb-8bbb-bbbbbbbbbbbb","clusterId":"cccccccc-cccc-4ccc-8ccc-cccccccccccc","access":[{"privileges":["data_reader"],"resources":{"buckets":[{"name":"events"}]}}]}
```

Basic credentials accept `data_reader` and `data_writer` privileges scoped to
buckets, optionally narrowing each bucket with `scopes` and each scope with
`collections`. For existing Capella roles, set `credentialType: "advanced"`,
supply `userRoles`, and omit `access`. The dashboard and `seekrit dynamic` support
both forms. Output contains `username`, `password`, and `clusterId`; use the
cluster's Couchbase connection string.

Capella has no native TTL for these credentials. The broker retains the returned
user ID and deletes the credential on revoke/expiry. If creation's response is
lost, recovery searches all pages for the exact lease username before deleting.
Failed deletion remains scheduled. This integration is for Capella, rather than
the separate Couchbase Server administrator REST API.

See the [CLI reference](/docs/reference/cli) and [API reference](/docs/reference/api) for commands and endpoints.
