enterprise capabilities
governance built into the action registry.
the same mutating flag that drives the approval queue drives the audit log and the RBAC check. governance isn't bolted on — it's the same mechanism the platform uses for everything.
workspace isolation
every business unit gets its own workspace. data, missions, subjects, and contacts are scoped. members operate within their workspace without reaching across.
role-based access control
actions optionally require specific roles. the same role check runs from the UI, the API, and the agent. no surface-specific bypass.
approval chains
supervised missions file decisions for human approval. build multi-step approval chains: marketing creates, legal reviews, exec approves.
full audit trail
every action — manual, approved via decision, or auto-executed by an autonomous agent — is logged with actor, timestamp, and context.
extensions for custom tools
build or install extensions that add agent tools (via MCP), UI panels, and API endpoints. the same registry, same validation, same RBAC.
API-first integration
every UI capability is an API endpoint. integrate nihmbus into your existing martech stack, trigger campaigns from CI/CD, or build custom dashboards.
faq
questions from enterprise teams
how does RBAC work?
every action in the registry optionally declares a required role. the same role check runs whether the call comes from the UI, the API, or the agent. roles are workspace-scoped and manageable by org admins.
can we build custom extensions?
yes. extensions contribute agent tools via MCP servers, UI panels via Module Federation, named actions via the registry, and workspace-scoped data via a built-in store. same validation, same permissions, same RBAC as native capabilities.
what about data residency?
workspace-level isolation and RBAC are available today. dedicated infrastructure and data residency controls are on the roadmap — contact sales to discuss your requirements.