Configure ChannelGate
Configure ChannelGate at the right scope. Gateway defaults establish the deployment, conversation settings adapt a workspace, and personal connections belong to the person using them.
Choose a scope
Section titled “Choose a scope”| Scope | What it controls | Where to start |
|---|---|---|
| Gateway | Chat connections, default agents, runtime, organization settings | Gateway settings |
| Conversation | Access, workspace, instructions, tools, and model defaults | Channel settings |
| Person | Personal accounts, credentials, and granted skills | Connected accounts |
| Thread | The engine/model selection and session for one piece of work | Model defaults |
Permissions depend on your role and the conversation’s management policy. An organization administrator manages gateway-wide settings; a conversation setting does not grant gateway administrator rights.
Configuration guides
Section titled “Configuration guides”Gateway settingsConnections, agent defaults, runtime, and organization settings.
Channel settingsConfigure the workspace, access, instructions, tools, and runtime.
Users and accessApprove users, assign administrators, and manage conversation access.
Engine authenticationSign in Claude and Codex, including a dedicated channel login, and pick a login that fits European data handling.
Model defaultsResolve gateway, channel, thread, and per-run selections.
Connected accountsSet up personal and shared service connections.
MCP configurationEnable native Cloud MCP tools and explicitly connected plugin servers.
Variables and secretsChoose a credential scope, visibility, and allowed destinations.
Skills and sourcesAdd sources, templates, grants, and governance settings.
Network policyConfigure network access and credential destination rules.
Storage and runtimeChoose folders and understand containers, mounts, and retention.
Automation settingsConfigure schedules, delivery, and background work.
Deployment settingsSet up the Linux service, reverse proxy, and operational environment.