---
title: Work across multiple accounts with Wrangler auth profiles
description: Maintain separate logins and switch between Cloudflare accounts per project, without re-running wrangler login.
image: https://edgetunnel-b2h.pages.dev/changelog-preview.png
---

> Documentation Index  
> Fetch the complete documentation index at: https://edgetunnel-b2h.pages.dev/changelog/llms.txt  
> Use this file to discover all available pages before exploring further. 

[Skip to content](#%5Ftop) 

# Changelog

New updates and improvements at Cloudflare.

[ Subscribe to RSS ](https://edgetunnel-b2h.pages.dev/changelog/rss/index.xml) [ View RSS feeds ](https://edgetunnel-b2h.pages.dev/fundamentals/new-features/available-rss-feeds/) 

![hero image](https://edgetunnel-b2h.pages.dev/_astro/hero.CVYJHPAd_26AMqX.svg) 

[ ← Back to all posts ](https://edgetunnel-b2h.pages.dev/changelog/) 

## Work across multiple accounts with Wrangler auth profiles

Jul 02, 2026 

[ Workers ](https://edgetunnel-b2h.pages.dev/workers/) 

[Wrangler CLI](https://edgetunnel-b2h.pages.dev/workers/wrangler/) now supports auth profiles: named logins that you scope to specific Cloudflare accounts and switch between automatically, based on the directory you are working in.

A profile is a named OAuth login bound to a directory. Commands run in that directory, and its subdirectories, use the matching account — so you can move between accounts without re-running `wrangler login`.

Use profiles to keep a separate login for each client when working at an agency, or to separate staging and production into different accounts. Pair a profile with an `account_id` in your [Wrangler configuration file](https://edgetunnel-b2h.pages.dev/workers/wrangler/configuration/) so a command cannot reach the wrong account.

```sh
# Create a profile for each account, choosing which accounts it can reach
wrangler auth create client-a
wrangler auth activate client-a ~/clients/client-a


wrangler auth create client-b
wrangler auth activate client-b ~/clients/client-b
```

Use the `--profile` flag to run a single command with a specific profile:

```sh
wrangler deploy --profile personal
```

In CI and other automated environments, `CLOUDFLARE_API_TOKEN` still takes precedence over all profiles.

For setup, the resolution order, and the full command reference, refer to [Authentication profiles](https://edgetunnel-b2h.pages.dev/workers/wrangler/profiles/).

```json
{"@context":"https://schema.org","@type":"BlogPosting","@id":"https://edgetunnel-b2h.pages.dev/changelog/post/2026-07-02-wrangler-auth-profiles/#page","headline":"Work across multiple accounts with Wrangler auth profiles · Changelog","description":"Maintain separate logins and switch between Cloudflare accounts per project, without re-running wrangler login.","url":"https://edgetunnel-b2h.pages.dev/changelog/post/2026-07-02-wrangler-auth-profiles/","inLanguage":"en","image":"https://edgetunnel-b2h.pages.dev/changelog-preview.png","dateModified":"2026-07-02","datePublished":"2026-07-02","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://edgetunnel-b2h.pages.dev/#website","name":"Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/"}}
```