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 Networks and create a network with non-overlapping CIDR.
2. Attach the network to the intended ownership boundary for your team or environment.
3. Verify the network appears under the expected section in the product UI.

Diagram (text)

Ownership boundary chosen -> network created -> future nodes inherit the expected context

Workflow 2: Register gateway control components

1. Use the supported community or hosted enrollment flow for the gateway services.
2. Verify the gateway control service appears in Agents.
3. Verify the gateway runtime 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 connect with CLI

1. Open Nodes and click Add node.
2. Choose Device or Server, then choose CLI.
3. Follow OS-specific install/auth/connect instructions.
4. Verify runtime with nanami status, nanami doctor, and nanami watch.

Detailed onboarding guide:

• Configure Add node in Dashboard
• Install Nanami CLI

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 access-scope 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.