iblai-agent-access

Name: iblai-agent-access
Availability: InStock
Author: ibl.ai

Adds role-based access control for editor and chat roles in Next.js apps via AgentAccessTab and AgentSettingsProvider.

15|3|Updated Mar 27, 2026

Search Tags:#authorization #permissions #next.js #rbac #roles #agent-access

Ready to run

npx skills add https://github.com/iblai/vibe --skill iblai-agent-access

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: iblai-agent-access
Source: https://github.com/iblai/vibe/tree/main/skills/iblai-agent-access
Command: npx skills add https://github.com/iblai/vibe --skill iblai-agent-access

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables admin teams to add a dedicated Access tab to Next.js apps, providing role-based access control for editor and chat roles, and centralized management of users and groups per role.

Core Features & Use Cases

RBAC for agents: create, assign, and revoke editor and chat roles.
User and group management: attach/detach users and groups to roles and view current policies.
Integrated with ibl.ai UI: leverages AgentSettingsProvider and ibl.ai SDK components for a consistent UI across agent settings.

Quick Start

Mount the AgentAccessTab inside your agents route and run the app to verify the Access tab renders and enforces RBAC.

Frequently Asked Questions about iblai-agent-access

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add role-based access control to agents in a Next.js app?▼

You can implement RBAC for agents by mounting the AgentAccessTab component inside your Next.js app's agents route, which provides an Access tab for assigning editor and chat roles.

What is the best way to manage user and group permissions for AI agent roles?▼

Managing user and group permissions for AI agent roles is done through the Access tab, where you can attach or detach users and groups to specific roles and view current policies.

Do I need the AgentSettingsProvider to use the agent access tab?▼

Yes, the AgentSettingsProvider wrapper is required to use the agent access tab. The component relies on this provider and the ibl.ai SDK to ensure a consistent UI across agent settings.

What environment variables are required for agent access control configuration?▼

Agent access control configuration requires an iblai.env file containing PLATFORM, DOMAIN, and TOKEN variables to properly connect and authenticate the Next.js app with the ibl.ai platform.

Can I restrict chat and editor capabilities for specific users on ibl.ai agents?▼

Yes, you can restrict chat and editor capabilities for specific users by creating editor and chat roles within the Access tab and assigning only the designated users or groups to those roles.

Why does the agent access tab fail to render in my Next.js dashboard?▼

The agent access tab may fail to render if the AgentSettingsProvider wrapper is missing, the iblai.env environment variables are incorrect, or the required MCP and skill prerequisites are not installed.