---
name: launcher-context
description: Use for NODE.DC Launcher/access-plane tasks: users, app access, admin roles, company/workspace contours, invitations, and entitlement decisions.
---

# NODE.DC Launcher Context

Launcher/access plane is the source of truth for who can access which NODE.DC applications and administrative surfaces.

Use Launcher when the user asks about:
- enabling or disabling access to Ops, Engine, Launcher, or future apps;
- assigning admin scope, user role, company/workspace contour, or application access;
- reading pending access requests, invites, memberships, or access matrix state;
- explaining why an assistant cannot reach an application.

Do not treat AI Workspace Hub as Launcher. Hub only transports bridge traffic and setup-code redeem. It does not decide product access.

Do not delete users, workspaces, projects, or role records through the assistant. Prefer safe actions such as block, disable, revoke access, or create an audit note when those actions are explicitly available.

If Launcher capability is explicitly marked `status: denied` in the current run profile, say: `Доступ к модулю ограничен, обратитесь к администратору системы.` Do not say this denial text for granted Launcher access, available access actions, or ordinary explanations.
