Common workflows

title: Common workflows description: Practical WebUI workflows for operators: create boundaries, enroll components, and troubleshoot.

This page focuses on repeatable operator workflows in WebUI.

Workflow 1: Create group and network boundary

1. Open Groups and create a group for an ownership unit (for example, platform).
2. Open Networks and create a network with non-overlapping CIDR.
3. Verify the network appears under the expected group.

Diagram (text)

Group created -> Network attached -> future nodes inherit ownership context

Workflow 2: Register gateway control components

1. Generate gateway-manager join key.
2. Run gateway-manager and verify it appears in Agents.
3. Generate gateway-daemon join key.
4. Run gateway-daemon and verify it appears in Gateways with healthy status.

Checks

• heartbeat timestamps update,
• runtime metadata (OS/interfaces) is present,
• region assignment matches your topology.

Workflow 3: Add a node and generate config

1. Open Nodes and add a node in the target network.
2. Use node details or connect flow to generate WireGuard config.
3. Apply config on test host and verify node state transitions to online.

Detailed wizard behavior and import flow:

• WireGuard device config wizard

Workflow 4: Validate routing behavior

1. Confirm the network routing policy (auto/manual, vpn_only/full_tunnel).
2. Verify ingress/egress device selection where applicable.
3. Check tunnel counters and handshake recency.

Workflow 5: Incident triage path

1. Start at Dashboard for broad impact.
2. Check Gateways and Agents for control/runtime drift.
3. Inspect affected Nodes and Tunnels.
4. Review recent policy or membership changes.
5. Roll back risky changes before introducing new ones.

Operational tips

• Keep naming and labels consistent across teams.
• Roll out network and routing changes in phases.
• Keep one known-good gateway path during major migrations.