How CityScreen Deals is put together

Every deal moves through a fixed sequence of seven stages: Inquiry, Negotiations, Reserved, Booked, Paid, Done, and Canceled. The stage graph is fixed. An administrator can customize the labels displayed for each stage, but the underlying states and their behavior remain the same.

A deal contains one or more proposals. The pricing engines for digital placements (frequency, duration, blocks, impressions) and printed placements (daily rates, sale rules) are fixed product logic. Discount tiers, organization-wide discount limits, and per-customer discount caps are built in.

Digital and printed displays are first-class objects with a fixed field set. The map view, availability timeline, and saturation calculations are product features.

The action hierarchy (read, update, delete) and scope hierarchy (own, group, any) are fixed. How roles compose and how field-level permissions interact with entity-level permissions are product behavior.

The password policy, two-step verification, protection against repeated failed sign-ins, sessions and the sign-in log are part of every organization. No setting switches them off. An administrator chooses their values, such as the minimum password length, and whether two-step verification is required.

An entity type is a schema that defines a kind of record — a document type, a counterparty type, a price list type, a report type, or any other structured record the organization needs. Each entity type has a set of fields (called variables in the API), which can be strings, numbers, dates, links to other records, sets, collections, maps, or computed expressions.

Every invoice, contract, booking order, or credit note you see in an organization is an entity type that an administrator defined, with templates and optionally a business process driving its lifecycle.

A customer is one kind of counterparty. The administrator can define additional counterparty types for agencies, media owners, subcontractors, or any other party the organization works with.

The built-in BPMN engine lets an administrator model and publish processes that automate work — user task assignments, email notifications, document generation, entity updates, and deal state transitions. Processes are defined per organization and can be started manually or triggered by entity events.

Criteria are 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.

Currency, user session duration, the password policy, the two-step verification policy, public inventory access, discount limits, deal stage labels, and proposal defaults are all per-organization settings. Currency is a single organization-wide setting.

OAuth applications, OpenID Connect, the LDAP directory, personal access tokens and app passwords let other programs call CityScreen Deals, sign employees in through it, or read its directory. These functions are licensed. If your organization’s license does not include them, contact CityScreen. An administrator registers the OAuth applications and LDAP consumers, and each employee creates their own tokens and app passwords.