Aligne Docs

Aligne helps teams map customer journeys and attach the actual communications customers receive — emails, SMS, chat messages, and more — directly to each step, so product, lifecycle, and operations teams share one source of truth.

Aligne is more than a workflow editor. In one place you can design workflows, review communications, collaborate with stakeholders, publish workflows, share them publicly, embed them anywhere, and reuse them as templates — with publication analytics on everything you share.

Sign in, pick a workspace, and you'll land on your Dashboard. From there you can create your first flow in under a minute.

On the Dashboard, click New flow and give it a name. Add nodes to represent each step a customer takes, then drag from one node's handle to another to connect them. Use annotations to capture context that doesn't belong on a step itself.

Projects help organize related flows on the Dashboard — by product, campaign, customer journey, department, or initiative. Group flows that belong together so the right context stays close at hand as your workspace grows.

You can create and manage Projects from the Dashboard and assign a flow to a Project when you create it or from its settings.

Attach a Communication Card — email, SMS, in-app message, push, or any other touchpoint — to any step in the flow. Open a card to preview the actual content exactly as a customer would see it, not just a description of it.

On Team plans, every edit to a card is versioned, so you can see what changed and roll back if needed.

Attaching communications. Each communication card is attached to one parent node at a time. Using Actions → Connect on an existing communication moves it to the newly selected parent — it does not attach the same communication to two nodes. To use similar content in more than one place, duplicate the communication instead.

Copy and paste. A copied communication needs a valid destination. Either select a destination flow node and paste onto it, or copy the communication together with its parent node so the pasted communication attaches to the pasted parent. If no valid destination is available, Aligne will ask you to pick one before pasting.

Duplicates are independent. A duplicated communication is always created as a new Draft, regardless of the source's status. It has its own identity and does not inherit approvals, comments, review history, or version history — edits to the duplicate never affect the original.

Every flow has a working draft and a published version. Edits stay in the draft as you work, so you can iterate freely without affecting what reviewers see.

When the flow is ready, publish it to update the published version. The draft remains editable for your next round of changes.

Publishing inside the workspace is separate from public sharing — a published flow is only visible outside the workspace once you publish it to a public link.

Any flow can be published to a unique public link. Anyone with the link can open the flow in a browser — no Aligne account required.

A public flow preserves the visual canvas experience: the workflow structure, the communications attached to each step, notes, and the relationships between steps are all there, exactly as your team designed them.

Teams use public links to share customer journeys, campaign flows, onboarding processes, documentation, and best practices — both internally with people outside the workspace and externally with clients, partners, and the wider public.

You stay in control. A public flow can be updated or unpublished at any time from Share → Publish to web. Unpublishing immediately removes public access to the link and any embeds using it.

Published flows can be embedded into websites, product documentation, knowledge bases, blogs, and resource centers using the embed code from the public link settings.

An embed is an interactive workflow, not a static screenshot. Readers can pan, zoom, and open steps and communications directly in place.

Embedded flows stay synchronized with the published version. When you publish an update, every embed reflects it — no re-exporting or re-uploading images.

When publishing a flow publicly, you can optionally allow visitors to create their own editable copy with Use as template. Visitors sign in or create an account, and the copy lands in their own workspace.

Templates accelerate onboarding, standardization, and reuse — a proven journey becomes a starting point instead of a blank canvas.

Creating a copy never modifies the original. The published flow, its communications, comments, approvals, and version history are untouched.

Every published flow includes publication analytics so you can see how it is being used:

• Views — how often the public flow was opened.
• Unique visitors — how many distinct people opened it.
• Template copies — how many visitors created their own copy.
• Embedded engagement — activity on the flow when it is embedded elsewhere, where applicable.

These are publication analytics, not marketing analytics: they describe how a published workflow is viewed and reused, not visitor identity or campaign attribution.

• Knowledge base. Publish an email verification journey and link it from your support knowledge base so agents and customers can see exactly what gets sent and when.
• Product documentation. Embed a lifecycle workflow into your documentation so readers explore the real journey instead of a screenshot that goes stale.
• Agencies and clients. Publish campaign architecture to a public link and share it with clients or partners who don't have an Aligne account.
• Reusable internal templates. Publish an approved onboarding flow with Use as template enabled so other teams can copy it and adapt it in their own workspace.

Workspace members collaborate on flows according to their assigned role. Creators can edit flows and their communication cards. Viewers can review flows and, where supported by the workspace plan, participate in comments.

Manage members and their roles from Workspace Settings.

Reviewers can leave comments on a flow as a whole or directly on individual Communication Cards. Feedback stays attached to the step or message it refers to, instead of getting lost across email threads and chat.

• Owner — full control of the workspace, including billing and member management.
• Admin — manages members, projects, and workspace settings.
• Creator — builds and edits flows and their communication cards.
• Viewer — reviews flows and, where the plan allows, participates in comments.

Aligne is both a workflow design platform and a workflow publishing platform. Teams design workflows, review the communications attached to them, collaborate with stakeholders, publish workflows, share them publicly, embed them anywhere, reuse them as templates, and track publication analytics — all from the same shared view.

Today that covers workflow documentation, communication planning, review, collaboration, governance, workflow publishing, public sharing, interactive embeds, reusable templates, sharing outside the workspace, and publication analytics. These are shipped, generally available capabilities.

It is intentionally not a project management tool, a marketing automation platform, or a communication delivery system. That focus is what keeps Aligne fast, clear, and useful for the teams who rely on it.

Can't find what you're looking for?