Publish Workflow
Publish → deploy or static config, with cabling, BOM, design doc — and the draft → pending → published review gate.
Publish is the finishing workflow: when the design is complete, one action walks you through validation and produces the deliverables — no hunting for separate buttons.
What Publish produces#
| Static configuration | Complete per-device, per-vendor CLI for the whole design. |
| Cabling schedule | Every link: A-end/B-end device, port, media, speed — ready for the rack team. |
| Bill of Materials | Chassis, line cards, optics, cables — and the passive patch panels and fiber LIUs the rack layout calls for — aggregated with quantities. |
| Design document | The drawing plus per-device summaries for the hand-off package. |
| Deploy | Alternatively, push toward deployment (Ansible-based) with credentials taken from the shared credential store — never embedded in the design. |
No account needed to generate#
Everything that is a stateless render of the design in your browser works without signing in: drawing, validation, config generation, the ZIP and Ansible bundles, the firewall handover, cabling and BOM CSVs, and the design document. An account is needed only for what an account actually holds — saving, sharing, the organization gallery, live labs, deploying to devices, and Azure.
Draft → pending → published#
Sharing a design to the organization gallery or as a public template goes through a review gate. Owners and admins publish directly. Everyone else's publish submits the design for review — it shows as pending (with a Withdraw action on the Publish row) until an owner or admin approves it from the admin page. Until then the design stays a draft, visible only to you and your collaborators — drafts never appear in the gallery, in search, or to other members.
Public vs. private#
Publishing defaults to private (your organization only). Choosing public shares the design as a community template — and first runs the scrubber, which strips company-identifying data: IP addressing, DNS/NTP servers, SNMP/syslog targets, AAA servers, and names.