iblai-access-tab

/iblai-access-tab

Add the agent Access tab -- role-based access management for agents. Lets admins assign editor and chat roles, add/remove users and groups per role, and view existing access policies in a table. This is one tab in the wider agent-settings family (access, api, datasets, disclaimers, embed, history, llm, memory, prompts, safety, settings, tools). All tabs share the same AgentSettingsProvider wrapper.

Do NOT add custom styles, colors, or CSS overrides to ibl.ai SDK components. They ship with their own styling. Keep the components as-is. Do NOT implement dark mode unless the user explicitly asks for it.

When building custom UI around SDK components, use the ibl.ai brand:

• Primary: #0058cc, Gradient: linear-gradient(135deg, #00b0ef, #0058cc)
• Button: bg-gradient-to-r from-[#2563EB] to-[#93C5FD] text-white
• Font: System sans-serif stack, Style: shadcn/ui new-york variant
• Follow the component hierarchy: use ibl.ai SDK components (@iblai/iblai-js) first, then shadcn/ui for everything else (npx shadcn@latest add <component>). Do NOT write custom components when an ibl.ai or shadcn equivalent exists. Both share the same Tailwind theme and render in ibl.ai brand colors automatically.
• Follow BRAND.md for colors, typography, spacing, and component styles.

You MUST run /iblai-test before telling the user the work is ready.

After all work is complete, start a dev server (pnpm dev) so the user can see the result at http://localhost:3000.

iblai.env is NOT a .env.local replacement — it only holds the 3 shorthand variables (DOMAIN, PLATFORM, TOKEN). Next.js still reads its runtime env vars from .env.local.

Use pnpm as the default package manager. Fall back to npm if pnpm is not installed.

Prerequisites

• Auth must be set up first (/iblai-auth)
• MCP and skills must be set up: iblai add mcp
• AgentSettingsProvider must wrap the route (see /iblai-settings-tab Step 2 if not already set up)
• Ask the user for a real mentorId (agent UUID). Do NOT invent one.

Step 0: Check for CLI Updates

Before running any iblai command, ensure the CLI is up to date. Run iblai --version to check the current version, then upgrade directly:

• pip: pip install --upgrade iblai-app-cli
• npm: npm install -g @iblai/cli@latest

This is safe to run even if already at the latest version.

Step 1: Check Environment

Before proceeding, check for an iblai.env in the project root. Look for PLATFORM, DOMAIN, and TOKEN variables. If the file does not exist or is missing these variables, tell the user: "You need an iblai.env with your platform configuration. Download the template and fill in your values: curl -o iblai.env https://raw.githubusercontent.com/iblai/vibe/refs/heads/main/iblai.env"

Step 2: Mount AgentAccessTab

The AgentSettingsProvider layout from /iblai-settings-tab Step 2 must already wrap this route. The provider supplies tenantKey, mentorId, username, and enableRBAC via context.

// app/(app)/agents/[mentorId]/access/page.tsx
"use client";

import { AgentAccessTab } from "@iblai/iblai-js/web-containers/next";

export default function AgentAccessPage() {
  return (
    <div className="flex h-full flex-col bg-white">
      <AgentAccessTab />
    </div>
  );
}

Step 3: Customize Labels (Optional)

AgentAccessTab renders with the default agent-facing copy (AGENT_ACCESS_TAB_LABELS). Override any string via the labels prop:

import {
  AgentAccessTab,
  AGENT_ACCESS_TAB_LABELS,
} from "@iblai/iblai-js/web-containers/next";

<AgentAccessTab
  labels={{
    header: { title: "Mentor access", description: "Manage who can edit or chat with this mentor." },
    table: { columns: { role: "Permission level" } },
  }}
/>;

Step 4: Use MCP Tools for Customization

get_component_info("AgentAccessTab")
get_component_info("AgentSettingsProvider")

<AgentAccessTab> Props

Import from @iblai/iblai-js/web-containers/next.

Prop	Type	Required	Description
labels	DeepPartial<AccessTabLabels>	No	Override user-visible strings (header, table columns, empty states, dialogs)
onPermissionsLoaded	(permissions: object) => void	No	Fired when RBAC permissions for /users/ and /groups/ are fetched on mount

Related Exports

From @iblai/iblai-js/web-containers/next:

• AGENT_ACCESS_TAB_LABELS -- the default agent-facing label bundle.
• AccessTabLabels -- type for the full label bundle (header, table, empty states, edit dialog, create dialog, role descriptions).

Step 5: Verify

Run /iblai-test before telling the user the work is ready:

1. pnpm build -- must pass with zero errors
2. pnpm test -- vitest must pass
3. Start dev server and touch test:

   pnpm dev &
   npx playwright screenshot http://localhost:3000/agents/<id>/access /tmp/access-tab.png
   

Important Notes

• Redux store: Must include mentorReducer and mentorMiddleware
• initializeDataLayer(): 5 args (v1.2+)
• @reduxjs/toolkit: Deduplicated via webpack aliases in next.config.ts
• Peer deps: sonner and @iblai/iblai-web-mentor must be installed (pnpm add sonner @iblai/iblai-web-mentor)
• Shared provider: AgentSettingsProvider must wrap the route at a layout level. See /iblai-settings-tab Step 2 for the full snippet.
• RBAC: The tab checks enableRBAC from the provider and rbacPermissions to gate add/edit actions. If enableRBAC is false (the default), all actions are permitted.
• Default roles: editor and chat. These come from DEFAULT_MENTOR_ROLES in the package and are not configurable via props.
• Brand guidelines: BRAND.md