Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
While user tokens act on behalf of a particular user and inherit a subset of that user's permissions, account owned tokens allow you to set up durable integrations that can act as service principals with their own specific set of permissions. This approach is ideal for scenarios like CI/CD, or building integrations with external services like SEIMs where it is important that the integration continues working, even long after the user who configured the integration may have left your organization altogether. User tokens are better for ad hoc tasks like scripting, where acting as the user is ideal and durability is less of a concern.
description: Explore account owned tokens in Cloudflare's API, ideal for CI/CD and integrations, with specific permissions and durability beyond user tokens.

## Create an account owned token

Expand Down
6 changes: 3 additions & 3 deletions src/content/partials/fundamentals/create-token.mdx
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
---
{}
{
description: "Create and manage API tokens in Cloudflare. Learn to set permissions, choose templates, and secure your tokens for effective API access."
}

---

import { Render } from "~/components"

:::note[Prerequisite]


Before you begin, [find your zone and account IDs](/fundamentals/setup/find-account-and-zone-ids/).


:::

1. Determine if you want a user token or an [Account owned token](/fundamentals/api/get-started/account-owned-tokens/). Use Account owned tokens if you prefer service tokens that are not associated with users and your [desired API endpoints are compatible](/fundamentals/api/get-started/account-owned-tokens/#compatibility-matrix).
Expand Down