Get your free AI plan
Docs / Words

Words

One table of the names used in the app, the MCP and these docs, what each means and what it was called before.

The app, the MCP and these docs use the same names for the same things. This table lists each name once: first the pages of a workspace, in the order of the menu, then the words that are not pages. The last column says what a page was called before the menu changed, so a search for an old name finds the new one.

WordWhereWhat it meansWas called before
HomeMenuWhere a workspace opens: how the setup is going, what was learned, found and handled, and what waits for you.Overview
WorkMenuWhat is being done, who has it, and what waits for you.Inbox
BoardWork › BoardWhere Work opens: the same tasks as Work › List, as columns by status or by who has it. The four chips, the search and the filters are the same.—
ListWork › ListEvery task in a table per status, each New, Planned, In progress, Waiting on a person or Done, with who has it, its workflow, how long it took and its tokens.Agent work, Signals, From your agents, Needs you, Setup check, Activity, Agents, Actions, Map activity
ResultsWork › ResultsHow many tasks came in, who handled them, how long they took and what they cost in tokens, by workflow.Value
WorkflowsMenuWhat is set up to be handled from now on, and how.—
The chainWorkflows › The chainHow each department is set up: its workflows, the playbooks in them, and the rules, policies and data behind them.—
All workflowsWorkflows › All workflowsEvery workflow, with its department and whether it runs, needs setup or is paused, and how many of its tasks wait on a person.—
PlaybooksWorkflows › PlaybooksHow your people handle a kind of case. An admin approves a playbook before an agent is handed it.What runs, Automations, Runs outside Maplith
RulesMenuWhat Maplith should tell you about, and what must always hold.Rules & know-how
Watch forRules › Watch forA rule that raises a signal when something happens. A rule can also be checked live in your own systems.Rules, Watches
Must holdRules › Must holdRules and decisions your own documents state, which Maplith and your agents keep to.From your documents, Decisions
FindingsMenuWhere your data does not work as your company intends. Each finding has its own page, with the evidence and what you want to happen.—
MapMenuHow your company fits together: its systems, its data and how work flows.Business map, Summary
SystemsMap › SystemsYour systems grouped by department, and how records flow between them.System map
AtlasMap › AtlasThe map as a graph: the objects, how they relate and how far each join can be trusted.—
ProcessesMap › ProcessesHow work moves between steps, discovered from the events your systems recorded.—
MetricsMap › MetricsThe figures worth tracking, with each one’s formula and the fields it rests on.—
TermsMap › TermsYour business terms, joins and columns to confirm, in your own words.Glossary
Personal dataMap › Personal dataWhere personal data sits in the map.—
SourcesMenuWhat Maplith reads and learns from. Maplith only reads your systems. It never writes to them.Data sources, Agents & access
IntegrationsSources › IntegrationsThe systems Maplith is connected to.Systems
ScansSources › ScansEvery scan and the map it built; the place to upload exports.Sources
AgentsSources › AgentsThe agents connected to the workspace, what each may do, and the actions they may take.Connections, Agent keys, Permissions, Policies, Actions, Usage
FieldworkSources › FieldworkHow you and your colleagues teach the map, and how to connect an agent.—
SettingsFoot of the menuThe workspace’s members, privacy, data, organisation, notifications and departments.—
HelpFoot of the menuAsk for help, and see your own reports.—
What's newFoot of the menuThe release notes of what changed in the app.—
Signal, taskThe MCP says signal; the app says task (Work)A signal in the MCP is a task in the app. It is one piece of work for an agent or a person, raised by a scan or a rule, and it is taken, done and recorded.—
ScanSources › ScansOne read of your systems and uploads that builds or rebuilds the map. A scan keeps the map it built, and an earlier one can be made current again.—
SourceSourcesA system Maplith is connected to, or a set of exported files from one. Each scan reads its sources.—
SystemSources › IntegrationsOne connected system, with its own page: how it is connected and read, the objects its files built, its scans, who owns it, the workflows that use it and what agents may do in it.—
FindingFindingsA place where the data does not work as intended, with its evidence. A person decides what it is, and an approved fix becomes work for an agent.—
RuleRulesA statement of what should hold or what to be told about. A rule that is breached raises a signal.—
Live checkRules › Watch forThe part of a rule an agent reports on. An admin binds it to the agent’s key, the agent observes in your own systems with its own connectors, and it reports what it saw.—
A workflowThe docs, Workflows and departments; its playbooks are in Workflows › PlaybooksA stored, named group of playbooks, many to many. What starts it, how it is done, who is involved, what limits it and where it works are derived from the playbooks, never stored. Its status is Running, Needs setup or Paused.—
A departmentSettings › Workspace › People › DepartmentsA named part of the company, with the people in it and the systems it uses, where departments are switched on. A workflow belongs to at most one.—
PlaybookWorkflows › PlaybooksYour people’s guidance for a kind of case. An agent is handed only the playbooks in use, and a playbook guides the work without granting permission.—
KeySources › AgentsWhat an agent connects with. An admin sets what it sees and what it may do.—
Key shapeThe MCP reference, Key shapesWhat kind of key a connection holds: read-only, acts with approval or autonomous, with its limits. The shape decides which tools the connection is listed.—
ApprovalWork › ListA person’s decision on a change an agent asked for or drafted. Nothing that waits for approval is applied before it.—
Action policySources › AgentsWhat a key may ask to do in your systems. Each request is answered allowed, denied or pending until an admin decides.—

One difference is worth knowing. What an agent reads as a signal over MCP, a person reads as a task in the app. It is the same piece of work under two names, and the Work the loop page follows it from the first read to the record of what was done.

← All docs · Markdown version