Skip to content
Moltaro Docs

Records

A record is one concrete business object in Moltaro. It might be a service request, asset, inspection, warranty case, customer resource, production item, approval, contact, entitlement grant, or another object your organization needs to manage over time.

The exact fields and screens depend on the record type. The purpose is the same: give the team one governed place for the facts, context, responsibility, and history of that object.

More than a form

Section titled “More than a form”

A record is not just the form used to create it. The form is one way to enter or change information, but the record can also have:

  • field values, such as names, dates, statuses, amounts, locations, and links;
  • a readable number, display name, and other presentation values;
  • related records or child information;
  • comments, files, tags, activity, and history when those features are enabled;
  • assignments, permissions, and field-level visibility rules;
  • links from boards, notifications, automation, reports, or module-specific workflows.

That is why two users may open the same record for different reasons. One person may update the operational facts, another may add evidence, another may review history, and another may only need the current status.

Where users see records

Section titled “Where users see records”

Users usually work with records through list pages, search results, detail pages, selectors, board items, notifications, related data sections, or reports. The same record can appear in several places, but it remains one business object.

For example, a warranty case could appear in a list of open cases, be linked from a customer record, be represented on a board, and show up in a report. Those surfaces are different views of the same underlying work.

What can change

Section titled “What can change”

Record changes are controlled by the record type and by access rules. Depending on configuration and permissions, a user may be able to:

  • create a new record;
  • edit some or all fields;
  • add comments, files, or tags;
  • assign responsibility;
  • archive or restore a record;
  • run actions or move related process work forward.

If a field or action is missing, disabled, or read-only, it usually means the record type, current state, or the user’s access does not allow that change.

Access affects what users see

Section titled “Access affects what users see”

Moltaro treats access as part of the record experience. A user might be able to read one record type but not another. A user might see a record but have some fields hidden. A linked record might appear as restricted if the link exists but the user cannot read the target record.

This is deliberate. Moltaro should not make restricted data look like it does not exist, but it also should not expose details a user is not allowed to see.

Where to go next

Section titled “Where to go next”