Your auditor will ask what your AI agents can touch. Have an answer ready in less than 5 minutes.

Trent Supports Organization Workspaces With Role-Based Access Control

Christoph Bartenstein
By Christoph Bartenstein
Aug 2026 • 0 min read

The Trent AI Security Engineer now supports Organization Workspaces, giving security, engineering, and product stakeholders one shared view of your security posture instead of separate individual accounts. Here’s how it works.

Organization Workspace View

Trent organization workspace: shared Projects list, organization menu, and workspace switcher with a personal account and Create Organization.

Creation of a Workspace

An admin creates the Workspace, invites the team by email, assigns roles, and connects a data source (e.g., GitHub). Any member can then run an analysis on a connected data source or open one a teammate has already run.

Roles

Organization Workspaces use role-based access control (RBAC), with Admin and Member roles in this release.

Admins manage members and role assignments, create GitHub App connections, and can view and revoke any member’s API keys. Members can work across all projects: running analyses, reviewing findings, and planning remediation.

Inviting a team member

Add member dialog with an email field, a role selector showing Admin and Member options, and a Send invite button.

Admin view for API keys in workspace

API keys dialog listing active OpenClaw keys for two members, with expiry dates, an Extend action, and a Create a key section.

Availability

Organization Workspaces are available to enterprise customers on request. To get started, contact us.