Concepts: the vocabulary of Rose Rocket

An agent is an AI helper in Rose Rocket that does a named job when asked: Rocky knows your whole organization, Rosie answers about the order you have open.

Anti-template means Rose Rocket starts from your own objects, boards and rules, not a fixed form, so the system matches how your operation already works.

Built with you means setting up Rose Rocket is shared work: the platform supplies the parts, your team arranges them, and Rose Rocket builds beside you.

Rose Rocket ships the orders, boards and record page every carrier and broker needs; your team shapes the fields, views and rules that make it yours.

An integration is a ready-made connection between Rose Rocket and another system, such as QuickBooks Online or DAT, that you switch on rather than build.

A permission is a yes-or-no attached to a role: whether its people can see a board, open a record page, read or change a field, create or delete records.

A role is what a person is in your organization, such as dispatcher, CSR, driver, partner or customer, and it decides what they can see and do.

A view is a saved tab on a board with its own filters, columns, sort, grouping and layout, so dispatch and finance see the same records different ways.

The detail view is the record page: one record's information laid out in sections and tabs, with panels for related things around it, for example ORD-28.

A document is a file attached to a record, such as a BOL, rate confirmation, POD or invoice, either uploaded or generated from a template you control.

A widget is one panel on a record page with one job: a short form, a map, the documents or a list of related records, for example Shipments on ORD-28.

A workflow is a rule that watches one kind of record and acts when something happens to it, for example Block edits on a sent invoice, which locks a bill.

A formula field computes its value from other fields on the record each time it is read, so nobody types it, nobody can edit it and it is never stale.

A board is the table of every record of one object, one row per record and one column per field, and it is what every entry in the left nav opens.

A field is one piece of information about an object, such as Status, Customer or Weight; its type decides how it is entered, filtered, totalled and shown.

An object is a type of thing your business tracks, such as Order or Customer: one list of fields every board, record page, workflow and document reads.

An organization is your company's own Rose Rocket: every board, record, user and role lives inside it, and each login lands in exactly one organization.

A record is one real thing Rose Rocket tracks: one row on its board and, once opened, one page of its fields filled in, for example the order ORD-28.