Skip to Content
Getting StartedOverview

Getting Started

This page outlines the path from an empty workspace to a running workflow.

Create the workspace

The setup wizard has eight steps: company, tools, people, connect, roles, accounts, invite, and review.

The wizard writes as you go, not at the end. Your organization is created in step 1. Only invitations wait for the final screen.

Connect the tools Alma should learn from

Alma can only learn from what it can see, so this is the highest-leverage step.

Connections are either Organization (connected once, for the whole company) or Personal (each member connects their own account). Start with the shared tools where the most work happens. You can add more later.

Let Alma build Memory

Once sources are connected, Alma starts building Memory: one topic per account, person, or goal, with structured facts and a running narrative. Every fact links to its source.

This takes time by design. Don’t build workflows on a map that hasn’t formed yet.

Define what matters

Memory is what Alma knows. Alignment is what your company is trying to do about it: the outcomes you’re driving toward, the groups accountable for them, and the directives that steer how Alma writes and acts.

You can write these by hand, or run a research campaign to have Alma propose them from your connected sources.

Build a workflow

A workflow is a graph of triggers, steps, and approval checkpoints. Build it on the canvas, or describe the change in chat and let Alma edit it for you.

A workflow is inert until you enable it. Draft freely — nothing on the canvas has consequences until you press Enable.

Set access and approvals

Before enabling, review the Access tab. Every tool the workflow touches is either Automatic or Needs approval, and any step can carry a human checkpoint.

Enable it and watch the runs

Press Enable, then watch the Runs tab. A run that hits a checkpoint pauses; the approver decides, and the run resumes from that step.

If something looks wrong, press Pause. The workflow returns to a draft and stops running.

Timeline

Connecting sources takes an afternoon. Memory forming is a background process measured in days. Building a workflow once the map exists is usually a single sitting.

Rolling this out across a company? Alma’s team can do it with you — a dedicated specialist maps your workflows, connects your stack, and tunes access to how your company runs. Email help@alma.team.

Two common mistakes

Building workflows before Memory has formed. A workflow grounded in a thin map produces thin work.

Over-restricting on day one. An approval on a step nobody meaningfully reviews adds latency without adding safety. Put checkpoints where judgment changes the outcome, and let the rest run.

Next

Last updated on