13 / Configuration

Guided Init & Scope

Pick organization, project, app and environment — filtered by what your role can actually see.

In this feature

Interactive project, app and environment pickers
Levels the token cannot see are never offered
Single-option levels selected automatically
Environments come from the app definition, not a fixed list
Escape to step back through the hierarchy
Final scope written to .cybsecrets.json

// In the console

What it looks like

cybsecrets init walks the hierarchy interactively and only asks for the levels your token can still resolve. If the credential grants a single organization, project or app, that level is selected automatically and skipped.

Guided Init & Scope — App selection under the Backend API project — only apps the authenticated role can read are listed.

Guided Init & Scope — detail — Environment selection — dev, staging and production, exactly as defined on that app in the console.

Fine-grained

Permissions shape the prompts

The picker is generated from the token's grants. An engineer scoped to one project never sees another tenant's apps, even by name.

Ergonomics

Skip what is obvious

A token bound to a single app resolves straight to the environment prompt, so CI configuration is one keystroke instead of four.

Reality

Environments are yours

Because environments are editable per app, teams running preview, qa or region-specific stages see them here without a CLI upgrade.

Included out of the box

Interactive project, app and environment pickers

Levels the token cannot see are never offered

Single-option levels selected automatically

Environments come from the app definition, not a fixed list

Escape to step back through the hierarchy

Final scope written to .cybsecrets.json

Next feature

Runtime Injection

Continue

Get started

One source of truth for every secret

Talk to the team