Core terms

These are the first Moltaro terms to know. Some terms have a simple user-facing meaning and a more precise configurator or developer meaning. This page starts with the user-facing meaning.

Product and data terms

Moltaro A low-code operations app platform for governed records, process, access, automation, reporting, and extension points.

Installation A deployed Moltaro runtime. In normal runtime use, an installation works against its configured workspace database.

Workspace The configured runtime environment where records, configuration, users, roles, modules, and operational data live.

Record One business object users work with, such as a request, asset, inspection, contact, production item, warranty case, or entitlement-related object. In technical documentation, this is often called an entity instance.

Record type The configured shape for a kind of record. A record type defines what fields, relationships, screens, access rules, audit settings, and behavior records of that kind can have.

Entity definition The configurator and developer term for a record type. If you configure fields, access, display behavior, runtime screens, or schema behavior, you are usually working with an entity definition.

Field A piece of information on a record. Supported field concepts include text, number, date, time, user, role, select, file, address, reference, table, and money-style values, depending on where the field is configured.

Relationship A connection between records or between a record and a responsible subject. Some relationships are simple references. Others carry governance meaning, such as owner, accountable, assignee, or reviewer.

Related data Information connected to the current record, such as linked records, child records, comments, files, tags, board items, activity, or other resources.

UI surface A configured place where a record is shown or edited, such as a form, card, table, detail page, drawer, or list page.

Work and process terms

Board A governed process surface for moving work through statuses, stages, handoffs, or cycles while keeping the underlying record intact.

Board item The process item on a board. A board item can have status, due date, responsibility, links, comments, attachments, history, and board-specific data.

Status The current stage or lane for work on a board.

Transition An allowed move from one status to another, sometimes with rules, required information, or permissions behind it.

Cycle A time-boxed or planning period for board work when a process is organized into iterations, periods, or batches.

Work Inbox The in-app place where users see notifications and active attention signals.

Notification A delivered message about an event or state change, with a link back to the related work when one is available.

Attention signal A current operational fact that needs attention, such as overdue work, due-soon work, missing ownership, or blocked work when a module provides that signal.

Access and governance terms

User A person who can sign in and work in a Moltaro installation.

Role A named group of capabilities. Roles help determine which users can see, change, administer, import, export, move, or otherwise act on product areas and records.

Permission A specific allowed capability, usually granted through a role or a configured access rule.

Assignment A link that says a user, team, responsibility group, or configured relation is responsible for a specific record or item.

Responsibility The business meaning behind an assignment, such as who owns, coordinates, works, or reviews a record.

Responsibility group A team, committee, department, region, or other group that can be assigned responsibility and used in access decisions.

Access model The configured approach for deciding who can see and act on records of a record type. Examples include broad permission-based access, record-scoped assignments, and contained child access inherited from a parent record.

Field access Rules that affect whether a user can see or edit specific fields, even when they can open the record.

Delegated access Access contributed by a source module or resource relationship, such as board responsibility granting access to the related work object.

Audit trail Recorded history that helps explain who did what, when, and against which record, item, role, or other resource.

Module and extension terms

Module A product area that adds runtime capability, such as Boards, Entitlement Operations, Work Inbox, Booking, or Currency Rates when enabled for an installation.

Entitlement A governed right to use, receive, access, or claim something. Entitlements are issued from configured models and plans, then tracked through lifecycle and ledger activity.

Resource A work object that Moltaro can describe, open, or attach activity to, such as an entity record, board item, entitlement, attention signal, role, or user.

Package A trusted extension or module artifact that can add runtime behavior, configuration, schema, services, or developer-facing integration surface.

Business logic Rules and code that automate or enforce behavior beyond manual editing, such as validation, before-save changes, actions, triggers, scheduled jobs, and C# extensions.

Next terms to learn

After these basics, continue with:

• Data and records for everyday record terms.
• Data structure for configurator terms.
• Access and governance for responsibility, permissions, and audit terms.
• Business logic for automation and extension terms.