Skip to main content

Settings — /rbac/settings

The Settings page exposes per-workspace RBAC configuration values — typed key/value pairs that tune how the RBAC service behaves for this workspace. It is admin-only.

The data behind the page is the rbacConfig(scopeId:) query (an array of RbacConfig rows) and the updateRbacConfig mutation (an upsert).

What you see​

  • + Add Setting button (top right) — opens the create form

Config list​

One card per configuration row. Each shows:

  • The key (e.g. session_timeout)
  • A type chip — one of string, number, boolean, json (drawn from valueType)
  • The value as a code-styled chip
  • The optional description
  • A relative Updated timestamp
  • An Edit pencil to re-open the form pre-filled

If no rows exist, an empty card invites you to add the first setting.

Create / Edit form​

When you tap + Add Setting or Edit on a row, an inline form appears with:

  • Key — string; disabled when editing (keys are the primary identifier)
  • Value type — one of string, number, boolean, json
  • Value — the actual value
  • Description (optional) — human-readable note for future operators

Save calls updateRbacConfig(input: { scopeId, key, value, valueType, description }), which upserts: if the key already exists the row is replaced, otherwise a new one is inserted.

Things you can do​

TaskHowPermission
View the workspace's RBAC configOpen /rbac/settingscanManageSettings (rbac:manage)
Add a new setting+ Add SettingcanManageSettings
Edit a settingPencil icon → SavecanManageSettings
Remove a settingNot exposed in the UI today; clear the value via APIAPI: updateRbacConfig

The page is fully gated on canManageSettings. Non-admin members get the standard Access Denied card and never load the rbacConfig query.

Common settings​

Settings are typed key/value pairs and the catalog of recognized keys is service-defined — the UI does not validate keys against a fixed list. Examples of keys you may encounter, depending on how your operator has wired the service:

  • session_timeout — TTL for cached permission decisions
  • cache_ttl_seconds — TTL for the RBAC permission cache
  • audit_retention_days — soft hint for retention
  • default_actor_type — what to assume when a check has no x-actor-type header
  • opa_required — whether Step 7 (OPA) is mandatory for this workspace

Refer to modules/rbac/specs/09-non-functional.md and your operator's runbook for the canonical list. Unknown keys are stored verbatim and ignored by the evaluator until a service consumes them.

Permissions you need​

canManageSettings is the gating capability. It maps to PBAC rbac:manage or auth-level module-rbac:config:write; workspace admins/owners bypass. The mutations behind the form (updateRbacConfig) are checked again at the service boundary against the config:write action.

Tips​

  • Keys are case-sensitive. Session_Timeout is a different setting from session_timeout.
  • The boolean and number value types are stored as strings on the wire — the UI does not coerce them. Save true (lowercase) or 0/1 rather than True / On to keep parsers happy.
  • The json value type expects a string that the consuming service will JSON.parse. The form does not validate JSON; check the value with a separate validator before saving.
  • Changes take effect on next read by the consuming service. There is no broadcast; in particular, cached evaluator decisions on existing requests are not invalidated until the next decision is evaluated.
  • For platform-wide defaults (e.g. system actor types, tenant-level toggles) use the global-rbac admin surface, not this page. This page is workspace-scoped only.