The Console

Alma has two environments. The workspace is where your team does their work — Home, Tasks, Spaces, and the decisions Alma brings them. The Console is where you configure the workspace.

These docs cover the Console.

Opening the Console

Click your workspace name in the top-left corner of the workspace, then Console.

Note

The Console requires Admin or Implementer access. A Member who follows a console link is redirected to their workspace. See Members.

Sidebar sections

Group	Sections	Docs
—	Search, Activity, Connections, Memory, Spaces	Connections, Memory, Activity
Agents	Workflows, Research, Skills	Agents
Alignment	People, Groups, Outcomes, Schema, Lessons	Alignment
Developers	Webhooks, API, MCP	Developers
Administration	Workspace, Members, Security, Billing	Administration

Help, at the bottom of the sidebar, opens these docs. Share feedback sends us a note with your current page attached.

Note

Press ⌘K anywhere in the Console to search across sections.

How the sections relate

Connections and Memory are the substrate: Connections decide what Alma can see, and Memory is what it made of that. Everything else depends on these two.

Agents is where work happens: Workflows are the automations, Research proposes what to build, and Skills are reusable instructions a workflow can load.

Alignment is the company’s intent: who’s accountable, what you’re driving toward, and how Alma should behave.

Developers and Administration are the edges — how other systems talk to Alma, and the workspace’s own settings.

Vocabulary notes

People vs. Members. A Person is a directory entry — anyone your company works with. A Member holds a seat and can sign in. Most People aren’t Members. See People.

Implementer is sometimes called Owners. Members has a person’s access level as Implementer, but a few pickers — a workflow’s visibility baseline, tool-access rule subjects — label the same level Owners. Same access level, different word depending on where you’re looking.

Workflows are agents in MCP. The Console and the public API both call them Workflows. MCP tool names are the exception — they call the same thing agent. See Developers.

Where things are governed

Some sections show a setting and link to where it’s actually managed. Workspace has a Workspace state panel — a read-only rollup of Memory, Outcomes, Connections, Members, and Workflows, each linking to its own section.

Security works the same way: it’s a catalog of controls, and most rows link to the surface where the real setting lives.