Skip to main content
Fibonacci’s governance layer gives organization owners and admins control over approval workflows, resource quotas, tool access policies, and the workflow registry. All governance mutations require at minimum the owner role.

Organization Governance Settings

Governance settings control which workflow actions require human approval before execution.

Get Current Settings

Update Settings

Field reference: The risk service enforces these flags at execution time — matching workflows are queued for approval rather than running immediately.

Quota Management

Quotas cap resource usage per organization. Plan defaults apply automatically; owners can override them up to platform-defined ceilings.

Get Quota Limits

Set Quota Overrides

Requires owner role. Overrides are validated against plan ceilings.
Override values must be positive and cannot exceed 100× the plan default for any key. Invalid values are rejected with a 422 response. See Security for details.

Tool Policy Administration

Tool policies control which tools organization members can use, and optionally restrict usage by role.

Organization-Level Tool Policies

The tool_name must exist in the tool registry. Unknown names return 422 with a hint to check GET /tools.

Role-Level Policy Overrides

Fine-tune access per role within the organization:
Role overrides take precedence over org-level policies. Evaluation order: role override → org policy → platform default (deny).

Workflow Version Management

Every deployment of a workflow creates a version snapshot. Admins and owners can inspect and roll back versions.

List Versions

Accessible to any active org member (member or viewer).

Inspect a Version

Returns the full workflow definition snapshot for that version.

Roll Back

Rollback creates a new version snapshot from the target version’s definition rather than overwriting history.
Response:

Workflow Registry

The workflow registry is an organization-level catalogue of approved workflow templates. Templates can be approved, deprecated, and archived through a structured lifecycle.

Lifecycle States

Approve as Template

Requires owner role. Only workflows that belong to an organization can be approved (personal workflows are rejected with 400).

Deprecate a Template

Archive a Template

Archived templates are hidden from the default registry listing and cannot be used as templates. This action is not reversible via the API.

List Registry Entries

Governance Reporting

Summary Dashboard

High-level governance health for the organization:

Paginated Audit Log

Full governance event history with pagination:
Optional filters:

Approval Statistics

Breakdown of approval activity by workflow, user, and category:

Access Requirements Summary

Next Steps

Security

Production hardening, secrets backends, and audit logging

Best Practices

Production workflow patterns