Key Concepts

A deal is a single commercial negotiation with a customer about advertising placement. Every deal moves through a fixed sequence of stages — Inquiry, Negotiations, Reserved, Booked, Paid, Done — and can be canceled at any point. A deal always has a customer; the customer record must exist before the deal is created. The stage sequence is the same for every organization and cannot be customized, though administrators can change the labels displayed for each stage.

Deals covers the deal pipeline, stages, and day-to-day deal work.

A proposal is a concrete offer inside a deal — what is being sold, over which periods, and at what price. Proposals have two independent characteristics:

Proposals are versioned through revisions. Each revision is an immutable snapshot; earlier revisions are preserved so the offer history stays inspectable.

Proposals covers proposal types, pricing, discounts, and revisions.

A display is a physical advertising asset — a digital screen or a printed surface. Displays have an address, geographic coordinates, a format, dimensions, and an installation kind (static, mobile, or route-based).

A face (called "side" in some parts of the interface) is one advertising surface on a display. A printed display can have multiple faces, each independently bookable. For digital displays, capacity is expressed through playback slots rather than faces.

Inventory covers digital and printed displays, the map, and availability.

Criteria are classification labels that can be applied to deals, customers, and inventory items. The administrator defines the available criteria; sales teams use them for filtering and segmentation.

Criteria covers setup and usage.

Saturation measures how much of the inventory is already occupied over a time period. Only proposals in the Reserved or Booked state count toward saturation; proposals still in negotiation do not. The saturation view helps sales managers see what is actually available to sell.

Availability and saturation covers the calculation and the timeline view.

An entity type is a configurable schema that defines a kind of business record. Entity types are how administrators model the specifics of their organization — document kinds, counterparty types, catalog directories, report templates, price lists, and more.

Each entity type belongs to one of eight super types: Document, Counterparty, Directory, Task, Proposal, Price List, Report, and Employee Group. The super type determines where records of that type appear in the interface and how the product treats them.

Each entity type has a set of fields. A field is called a "data type" in the interface and a variable in the API. Fields can be strings, numbers, dates, links to other records, sets, collections, maps, or computed expressions.

The entity system is the dedicated section for entity types, fields, and expressions.

A business process is a BPMN 2.0 workflow modeled in the application and executed by the built-in process engine. Processes automate work that would otherwise require manual coordination — user task assignments, email notifications, document generation, entity updates, and deal state transitions.

Processes are defined per organization, versioned, and can be activated or deactivated. A process can be started manually from the Tasks page or triggered automatically by an entity event.

Process automation covers modeling, publishing, and running processes.

A task is a unit of human work created by a running business process. When a process reaches a user-task step, the engine creates a task and assigns it to an employee or offers it to a group of employees (a candidate group, which maps to an employee group).

Tasks appear in the Tasks section, show their position on the process diagram, and are completed through forms.

Working on tasks covers the task list and task completion.