Credential Access Levels

Credential Access Levels

Greentic resolves a tenant’s credentials — MCP server tokens, LLM API keys, OAuth app secrets, and extension credentials — through a scope hierarchy: a more specific scope (team, user) overrides a broader one (tenant default). That answers which value is used. Access levels answer a different question: who is allowed to set the value at which scope.

Every credential carries an access level (the override_policy field):

Level	Meaning
Open	A team or flow may override the admin value. This is the default and matches the previous behaviour.
Locked	The admin (tenant-default) value is forced. Lower scopes cannot override it, and the value is required to exist.
Required	The admin sets no value, but marks the credential mandatory. It must be supplied at a lower scope — a team, a flow, or by the LLM at runtime.

ヒント

Think of it as the three places a secret can live: some are set once by the admin for the whole tenant (Locked), some the admin provides as a default that a flow may replace (Open), and some the admin deliberately leaves to the flow author or to runtime (Required).

Setting the access level

Open Settings → Integrations (or a tenant’s credential tabs) and pick the credential — an MCP server, an LLM provider, an OAuth app, or an extension credential. Each form has a Tenant access selector:

• Open — teams/flows may override
• Locked — force this value
• Required — must be set lower down

Validation keeps the choice consistent: a Locked credential must have a value to lock onto, and a Required credential must not carry one (the value comes from a lower scope). Access level is a tenant-default (admin-level) decision, so it is not offered on a team-scoped row.

What the flow author sees

In the Designer’s composer, a credential’s access level changes how its input renders:

• Locked — the input is read-only and labelled “Set by admin”; the flow author cannot change it.
• Required — the input is marked mandatory so the flow author knows they must provide a value.
• Open — the input behaves as before; a value here overrides the admin default for this flow.

How resolution enforces it

At read time the resolver honours the access level on top of the scope walk:

• Open — walk user → team → tenant-default and take the first value.
• Locked — read only the tenant-default (admin) value and fail closed if it is missing; lower-scope values are ignored.
• Required — walk the scopes; if nothing is set anywhere the credential is reported as required but unset rather than silently absent, so the gap is visible instead of surfacing at runtime as a mysterious failure.

ノート

Access levels apply to MCP servers, LLM providers, OAuth apps, and extension credentials. Categories such as SSO and deploy credentials keep the Open behaviour and can adopt access levels later without any change on your side.