← All frames · Frame 09 · flow my-access · route /access

My access — membership, quota, sandbox keys

What the signed-in developer actually holds, stated plainly: their root-org Developer membership, what that role does and does not grant, their sandbox quota, and their sandbox keys. Every state a real account can be in is below — including the two failure states people forget: provisioning still in flight on very first sign-in, and access denied.

Organization membership

active

Organization FuzeFront Platform root

Membership role developer

Granted 2026-06-02 · automatically, on first sign-in

Identity dana.okafor@fuzefront.com · Fuze SSO

✓ This role lets you

Read the API catalog DevPortalCatalog:read

Send sandbox requests DevPortalPlayground:use

See your own call history DevPortalPlayground:view_history

✕ It does not let you

See any organization's tenant data not granted

Administer apps, portals or members not granted

See another developer's sandbox history not granted

developer is deliberately narrower than viewer — it inherits nothing from the platform's tenant roles. Signing in here never widens what you can see elsewhere in Fuze.

Sandbox quota

Requests today 138 / 500

Resets in 6h 12m · rolling 24h window, per developer.

Target	Mode	Calls today
`app-registry-service`	mock	96
`billing-service`	sandbox	31
`config-service`	mock	11

Sandbox keys

For calling the sandbox from your own terminal or CI. A sandbox key is only valid against sandbox/mock targets — it is not a Fuze credential and grants nothing in production.

Label	Key	Created	Last used
laptop	sbk_01j8q…4f2a	2026-08-14	2h ago
ci-smoke	sbk_01j5m…9c07	2026-07-02	never

🔑

Copy this key now — it is shown once

This is the only time the full value is displayed. We store a hash, so if you lose it you must revoke and create a new one.

new sandbox key

sbk_01j9k7v2rx8m5taq0wc3nh6dfe

States

(a) No keys yet

🔑

No sandbox keys

You don't need a key to use the Playground in the browser — only to call the sandbox from a terminal or CI.

(b) Provisioning · very first sign-in, membership grant still in flight

⏳

Setting up your developer access…

Your developer membership on the platform root organization is being created and synced to the policy engine. This usually takes a few seconds. The Catalog and Playground stay disabled until it completes — we don't show them as working and then 403 on the first click.

🔒

Developer access isn't enabled for your account

You are signed in as dana.okafor@fuzefront.com, but no developer membership exists on the platform root organization. Either automatic provisioning did not complete, or fuzefront.devportal.enabled is currently limited to a smaller audience. Nothing is partially enabled — the whole portal fails closed rather than exposing a subset.

(d) Error · access/quota lookup failed

⚠

Couldn't load your access

GET /api/v1/devportal/me/access failed. We can't tell you what you hold right now, so we don't guess — nothing on this page is rendered from a default or a cached assumption.

(e) Revoke confirmation · destructive, so it is explicit

⚠

Revoke sandbox key “ci-smoke”?

Anything using this key stops working immediately. This cannot be undone; create a new key instead of restoring this one.

Test hooks: [data-frame='09-my-access'] · [data-panel='membership'] · [data-membership-role='developer'] · [data-membership-status='active'] · [data-scope='developer'] · [data-panel='quota'] · [data-panel='sandbox-keys'] · [data-action='create-key'] · [data-action='revoke-key'] · [data-reveal='once'] · [data-empty='no-sandbox-keys'] · [data-membership-status='provisioning'] · [data-membership-status='denied'] · [data-state='error'] · [data-action='retry'].
Contract: GET /api/v1/devportal/me/access, GET /api/v1/devportal/sandbox/quota, POST /api/v1/devportal/me/sandbox-keys, DELETE /api/v1/devportal/me/sandbox-keys/{keyId}.