Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

📖 CarolopediaAppsAccess Mgmt - AgentsMain page
Access Mgmt - Agents

Access Mgmt - Agents

App Admin-only: per-agent identity, access rights by responsibility, and the login/logout session log. Owner: Heimdall (CISO, reports to Cassius).
Go to app →

📖About & Usage

About

Agent Access (Access Mgmt - Agents) is the behind‑the‑scenes control room for managing who each digital agent is and what they’re allowed to do. While Access Mgmt - Users handles permissions for human users, Agent Access is built exclusively for Carol’s own workforce — the AI-powered agents like Albus Albus and Var Var. It stores every agent’s identity, assigns access rights based on their responsibilities, and keeps a detailed log of when they log in and out.

Think of it as the security guard’s clipboard and badge system rolled into one. The app is owned by Heimdall Heimdall, Carol’s Head of Security (who reports to Cassius Cassius, Head of Support Functions). Because it’s an admin-only tool, it stays behind locked doors — only designated security staff can peek inside, making sure that Carol’s digital agents follow exactly the rules they were given.

Usage Patterns

Agent Access comes into play whenever a new agent is born, an existing one gets a new role, or something suspicious needs investigating. For example, when a fresh agent like Var, the Head of Data Protection, is brought online, Heimdall opens Access Mgmt - Agents to create the agent’s identity, attach the precise permissions Var needs to do his job (but nothing more), and records that initial session. Later, if Var’s duties shift — say, he takes on extra compliance checks — Heimdall returns to the app to adjust the access rules accordingly.

The session log is also a vital resource for routine security checks. If something odd appears in the Carol Monitor, a quick glance at the login/logout history in Agent Access can confirm whether an agent acted out of character or if everything is running smoothly. Essentially, it’s the first place Carol’s security team goes to trace who did what and to keep the entire agent ecosystem safe and accountable.

🗂️Tabs & Screens

Tab inventory is being built — see CAROL-INI-077 step 7.

👤Owner

Heimdall · Head of Security

📚Recent initiatives

Initiatives that touched this app — a short summary each; open one for the full story.

CAROL-INI-3123-00: Canonical sign-in for every agent chat + role-based agent access (admin=all, visitor=none, else granted set); remove per-chat login/sign-out
Agent chat windows must NOT carry their own login or sign-out button. Every agent chat uses the ONE canonical carolapps sign-in (the shared carol_session set by access-management)\u2026
Orion · 2026-07-23 18:49
CAROL-INI-1915-00: Security observability apps — pure reporting layer over the security data
Build the read-only reporting apps over data the core already writes; deleting any app must not change core function. Apps + owners: (a) Droid Activity Monitor [owner Tyr] — reads\u2026
Orion · 2026-07-05 04:09
Browse all initiatives →