Glossary

The words MaxSuite uses, in alphabetical order. Each links to, or names, the page that explains it.

Action class: what kind of act a tool is: read, write, destructive, external or spend. It decides what the approval check does when no rule says otherwise. See Agents and approvals.

Administrator: a person who passes every permission check in their own organisation. Most modules still narrow which records an administrator sees. See People, roles and permissions.

Agent: an AI assistant, defined on Agents → Agents, that does things by calling tools. It always acts for a person and can never do more than that person may. See Agents.

Alert destination: a named place that is not a person, such as an on-call group chat, that monitors and reports send to. See Notifications and alerts.

API key: a password for a program, made on Account. It is narrowed by permissions, modules, read-only and an expiry date, and is never stronger than the person who made it. See API keys and MCP access.

Approval: a request for a person to allow one tool call. It is answered on Agents → Approvals or in a linked chat. See Approvals.

Approval rule: a standing answer (allow, ask or deny) about a kind of action or one tool. No rule can allow spending. See Agents and approvals.

Audit trail: the record of every change and who, or which agent or key, made it. See People.

Automation: a "when this happens, do that" you make yourself on Automation → Automations, from a template or by describing it. See the Automations page.

Bank feed: a connection to a bank that pulls account lines into MaxSuite, where they are compared with your books and held lines wait for a person. See the Bank feeds page.

Bills inbox: a mailbox MaxSuite reads for invoices sent to you, turning each into a bill to approve. See the Bills inbox page.

Blog: a public set of articles made in the Blog module and served as a blog site. See Public sites.

Books: the double-entry accounts of a business, kept by the ledger module. Also called the ledger. See Books.

Booking page: a public page where people pick a free time with you. See Booking and Public links and sharing.

Brain: a project's memory: what it is for, what was decided and why, and what is true about it. See Brain.

Capability: something one module offers that others use, such as llm.chat from the AI module. See Workspaces and modules.

Chain: a run of agent steps that carries on by itself, can be paused and resumed, and can be saved as a playbook. See the Chains page.

Channel: a way a notification reaches a person: Telegram, email or browser push. See Notifications and alerts.

Connected app: an outside app, such as Claude, connected by signing in rather than with a copied key. It acts as the person who connected it. See Connected apps.

Connector: an outside service set up once on Connections → Connectors, so people can add their own accounts at it and agents can use its tools. See Connectors.

Contact: a person or company your work is about, kept once in Work → Contacts and linked from mail, chats and tasks. See the Contacts page.

Conversation: a thread with a customer on a messaging channel such as WhatsApp, answered by a person or an agent. See the Conversations page.

Core: the part of MaxSuite that is always present: sign-in, organisations, permissions, notifications, themes and secrets. Its tools use the id core. See Workspaces and modules.

Digest: one summary of your unread notifications, sent at a set hour or on request. See Notifications and alerts.

Enabled: switched on for the whole MaxSuite. One of the three things a module needs before it shows. See Modules.

Entitled: allowed for your organisation. One of the three things a module needs before it shows. See Modules.

Entity: in the books, a business whose accounts are kept. See Books.

Event rule: a rule that does something when a module reports an event, such as telling a person. See the Event rules page.

Finding: a problem a module found on its own and keeps until it is resolved. See Infrastructure map.

Graphite: a theme of neutral greys with no colour accent. See Appearance and themes.

Handle: an account at an outside service that an agent acts as. An agent acts only as the handles it was given. See Connectors.

Integration: a connected account at an outside provider, such as a registrar, whose domains and servers come into MaxSuite. See Integrations (provider accounts).

Kit: a ready-made set of things a new project starts with, such as tasks and an agent team. See the Kits page.

Landing site: a product's public front website, served under /l/. See Public sites.

Ledger: another name for the books. See Books.

Lent connection: an AI connection one organisation lends another, with a monthly limit. See Organisations.

Librarian: a helper that files loose records, such as domains or servers, into the projects they belong to, for a person to accept. See the Librarian page.

Marketplace: searching outside supplier markets for products and offers. See the Marketplace page.

MaxFill: the separate fulfilment service MaxSuite connects to for packing and shipping orders. See the MaxFill page.

MaxIAM: MaxSuite acting as the sign-in for other apps. See MaxIAM: sign-in for other apps.

MaxPass: the password store, shown as Passwords under Connections. Agents can have a password used for you but are never shown it. See Public links and sharing.

MaxSuite: this product. In the app it often calls itself Max.

MCP: the Model Context Protocol, which AI clients use to call tools. MaxSuite serves every tool you may call at your address followed by /api/mcp. See API keys and MCP access.

Module: one part of the product, such as Tasks or Costs, with its own screens, permissions, jobs and tools. See Workspaces and modules.

Named secret: a key or password entered once by a person under a short name and referred to by that name. Nobody can read it back. See Named secrets.

Organisation: one business on a MaxSuite, with its own people, teams, data and settings. The code calls it a tenant. See Organisations.

Permission: one named right, such as costs:read. You need every permission an action asks for. See People, roles and permissions.

Pipeline: work that runs through recorded stages worked by agents, with gates where a person decides. See Pipelines.

Platform administrator: an administrator of the organisation that runs the MaxSuite. Only they can change the whole MaxSuite. Some screens also need a platform right, such as Platform: modules, Platform: sso or Platform: requests. See Modules.

Posting: booking an entry in the books. See Books.

Product: a group of modules offered as one thing. Granting it grants every module in it. See Modules.

Public link: a link anyone holding it can open without signing in. See Public links and sharing.

Readiness: how ready a project is, judged by checklists. See Readiness.

Reply desk: one place to see and answer mentions and replies on social accounts. See the Reply desk page.

Role: a named list of permissions that people hold. See People, roles and permissions.

Sensitivity: a module's declaration that it touches money, auth or secrets. An agent's changes there go to a person. See Agents and approvals.

Share: access to one record given to a named person or team, at a level such as viewer or editor. See Sharing and visibility.

Skill: a set of instructions an agent loads when it needs them. See Skills.

Sourcing: finding suppliers for the products you sell. See the Sourcing page.

Stock: how many of each product you hold, and where. See the Stock page.

Supplier order: an order you place with a supplier, tracked until it arrives. See the Supplier orders page.

Support ticket: a customer's question or problem, tracked in Work → Support until it is solved. See the Support page.

Team: a group of people in an organisation. What is shared with a team reaches all its members. See Organisations.

Tenant: the code's word for an organisation.

Tool: one action a module offers to agents and programs, named <module>.<verb>, or <module>__<verb> over MCP. See API keys and MCP access.

Topology: the infrastructure map. See Infrastructure map.

Two-factor sign-in: a six-digit code from an authenticator app asked for after your password. See Profile and sign-in.

Vault: a held balance, such as petty cash or a bank account, that changes only by recorded movements. See Vaults.

Visibility: which records you see within a module. See Sharing and visibility.

Wallet: a crypto wallet an agent can propose transfers or swaps from, each one approved by a person. See the Wallets page.

Workspace: in older pages, the same as an organisation. Not the same as the Workspaces module, which prepares folders on a device for an agent. See Workspaces.