Skip to content

governance (RBAC, audit trail, policy guardrails) #32

Description

@ashupednekar

Summary

Introduce governance controls for multi-user and multi-tenant operation.

Motivation

As adoption grows, operational safety requires RBAC, policy controls, and auditability.

Proposal

  • Org/project-level RBAC model.
  • Audit logs for function/config/deploy/invoke admin actions.
  • Policy guardrails (OPA/Kyverno-compatible) for unsafe configs.
  • Approval workflows for production-impacting changes.

Acceptance criteria

  • Role model is documented and enforced by API.
  • Audit events are emitted for critical actions.
  • Policy engine can block disallowed runtime/deploy configs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/platformPlatform architecture and infrastructurearea/portalPortal API/UI and project managementarea/securitySecurity vulnerabilities and hardeningenhancementNew feature or requestpriority/p2Medium priority

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions