📖About & Usage

About

Requests Inbox is the private administrative front door for incoming requests to use Carol’s capabilities and subscriptions. It gives authorised administrators one clear place to review what has arrived, understand what access is being sought, and guide each request toward the appropriate next step. The app exists to keep these decisions orderly and visible instead of scattering them across conversations or leaving requesters wondering what happened.

The inbox is owned by Carol, Carol, and is restricted to administrators. It works alongside dedicated services such as Access Mgmt - Users for user access, Access Mgmt - Agents for agent access, and Model Subscriptions for model subscriptions. Requests Inbox focuses on receiving and reviewing requests; those other apps handle their own specialised parts of the wider process.

Usage Patterns

Requests Inbox is used whenever a new capability or subscription request enters Carol’s administrative workflow. An administrator opens the inbox, checks the request’s purpose and relevant details, and determines which team or service should handle it. Because the app is private, ordinary users and agents do not browse the administrative queue themselves.

For example, suppose someone needs access to an approved AI capability for a new piece of work. Their request appears in Requests Inbox, where an administrator can review it, identify any missing information, and direct it to the appropriate access or subscription service. The inbox acts like a friendly reception desk: it does not perform every downstream task, but it makes sure each arrival is noticed and sent to the right place.

🛰️Updates

Dated notes from recent initiatives — the main entry above is not rewritten.

🗂️Tabs & Screens

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

👤Owner

📚Recent initiatives

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