Lindy Enterprise RBAC

Overview

Manage team-level access control for Lindy AI agents and automations. Lindy organizes access around workspaces where agents live, with team members assigned Owner, Editor, or Viewer roles that govern who can create, modify, run, or merely observe AI agents and their execution history.

Prerequisites

• Lindy Team or Enterprise plan (per-agent pricing applies)
• Workspace owner or admin privileges
• Team members invited to the Lindy workspace

Instructions

Step 1: Map Organizational Roles to Lindy Permissions

Step 2: Configure Team Membership via API

Step 3: Restrict Agent Visibility per Team

Step 4: Audit Agent Access

Step 5: Enforce API Key Scoping

Create separate API keys per integration rather than sharing a single workspace key. Rotate keys on a 90-day schedule and revoke immediately when a team member leaves.

For detailed implementation code and configurations, load the reference guide: Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)

Error Handling

Examples

Basic usage: Apply lindy enterprise rbac to a standard project setup with default configuration options.

Advanced scenario: Customize lindy enterprise rbac for production environments with multiple constraints and team-specific requirements.

Output

• Configuration files or code changes applied to the project
• Validation report confirming correct implementation
• Summary of changes made and their rationale

See security implementation details for output format specifications.

Resources

• Official security documentation
• Community best practices and patterns
• Related skills in this plugin pack