Best first template
UML sequence diagram for login, token refresh, and service authorization.
Use diagram.now when a software design needs a diagram before it needs a formal tooling decision. Draft UML class diagrams, sequence diagrams, component diagrams, deployment diagrams, and architecture sketches in the browser.
UML sequence diagram for login, token refresh, and service authorization.
Send search visitors to the browser editor first. Ask for Marketplace install only after they know the diagram is useful.
When the diagram belongs in a spec, runbook, ADR, or process page, install diagram.now so it stays editable beside the docs.
A UML diagram helps reviewers understand structure and flow before they debate implementation details. Keep the first version simple: the classes, services, dependencies, or sequence that matter for the decision.
Use UML for API auth flows, service boundaries, deployment topology, domain models, major classes, state transitions, and integration contracts.
If the diagram becomes part of an ADR, RFC, implementation plan, or onboarding page, use the Confluence app so teammates can update the visual where the discussion already happens.
Use the browser editor for the first draft. If the diagram becomes team documentation, install diagram.now from Atlassian Marketplace and keep it editable inside Confluence.
Use diagram.now for common UML-style diagrams including class, sequence, component, deployment, package, activity, and state-oriented visuals.
The web editor should be positioned as the free entry point. If a team wants Confluence-native editing, point them to the Atlassian Marketplace app.
Start with a sequence diagram for one user action or a class/domain model for one bounded part of the system.