#### Release Notes: Restricted visibility for AI Catalog (Iteration 1) **Share AI agents and flows across your company, without exposing them to the world.** The AI Catalog now supports a new **Restricted** visibility tier for agents, flows, and skills, closing the long-standing gap between _Private_ (one project only) and _Public_ (visible to everyone on GitLab). When you mark an item as Restricted, it automatically becomes discoverable and reusable across every group, subgroup, and project within your Top-Level Group (TLG) hierarchy, with no duplication required. **Why it matters:** Enterprise teams no longer have to choose between locking an agent to a single project or exposing proprietary prompts and company-specific logic to all of GitLab. Your developers get company-wide discoverability and a single source of truth, while your organization keeps sensitive prompts and PII safely inside its walls. This is the first iteration of a broader vision. A follow-up iteration will introduce _pool_-based sharing, letting Owners share Restricted items across multiple TLGs they administer. Track progress on the parent epic [&20707](https://gitlab.com/groups/gitlab-org/-/work_items/20707) and this iteration's epic [&22590](https://gitlab.com/groups/gitlab-org/-/work_items/22590). > [!note] > > This issue is part of a collection of issues to deliver **Iteration 1** of the epic https://gitlab.com/groups/gitlab-org/-/work_items/20707 (as outlined in https://gitlab.com/groups/gitlab-org/-/work_items/20707#note_3439997863). > > * See the epic https://gitlab.com/groups/gitlab-org/-/work_items/20707 for greater overall context > * Related child issues of the epic share the name **Restricted visibility - Iteration 1 (Restricted to TLG hierarchy)**