org
Work with Sentry organizations
Commands
Section titled “Commands”sentry org list [<filter>]
Section titled “sentry org list [<filter>]”List organizations
Arguments:
| Argument | Description |
|---|---|
[<filter>] |
Only list organizations whose slug or name fuzzy-matches this text or matches this glob |
Options:
| Option | Description |
|---|---|
-n, --limit <limit> |
Maximum number of organizations to list (default: "25") |
-f, --fresh |
Bypass cache, re-detect projects, and fetch fresh data |
-a, --account <account> |
Only list organizations of this account (email, username, or account id; |
Examples:
# List organizationssentry org list
# Only organizations whose slug or name matches (fuzzy, best matches first)sentry org list acme
# Only organizations matching a globsentry org list 'acme-*'
# Only one account's organizationssentry org list --account jane@acme.com
# Same email on several servers: add the serversentry org list -a jane@example.com:sentry.io
# Output as JSONsentry org list --jsonsentry org view [<org>]
Section titled “sentry org view [<org>]”View details of an organization
Arguments:
| Argument | Description |
|---|---|
[<org>] |
Organization slug (optional if auto-detected) |
Options:
| Option | Description |
|---|---|
-w, --web |
Open in browser |
-f, --fresh |
Bypass cache, re-detect projects, and fetch fresh data |
Examples:
# View organization detailssentry org view my-org
# Open in the browsersentry org view my-org -wAll commands support --json for machine-readable output and --fields to select specific JSON fields.
Filtering organizations
Section titled “Filtering organizations”Pass a filter to sentry org list to only list organizations whose slug or
name matches it, best matches first. Matching ignores case and accepts exact
matches, prefixes, substrings, small typos, or a glob such as 'acme-*'.
Multiple accounts
Section titled “Multiple accounts”With several stored accounts (see sentry auth list), sentry org list lists
the organizations of every logged-in account together, each fetched with that
account's own credentials on its own server, plus an ACCOUNT column naming
each account as <email>:<server> — the form --account and
sentry auth login accept. An
organization reachable from several accounts on the same server is listed once,
under the active account if it is one of them, else the most recently used.
Accounts whose login fails are skipped with a warning. SENTRY_HOST/SENTRY_URL limits the list to accounts on that server,
and --account to a single account. The stored active account never changes.
With --json, each entry's account carries that notation as name, with its
parts alongside: email (or username) and server.
$ sentry org listSLUG NAME ACCOUNTmy-org My Organization jane@example.com:sentry.ioacme-internal Acme Internal jane@acme.com:sentry.acme.com