What You Can Edit

Almost every field on a screen or a face belongs to the source system. Four settings on a face belong to the operator.

Read this page before planning any work that depends on values typed into CityScreen Context, because everything outside the four is replaced the next time the catalog is pulled.

This page is for owner, admin and manager employees, who are the roles the platform accepts edits from. Viewers and moderators see the face detail page in read-only form.

The four editable settings

They are edited together on a face’s detail page and saved in one action.

Setting	What it is
Format	The commercial format label — billboard, supersite, cityboard, media facade and so on. Chosen from the list the deployment defines.
Camera	Whether this face has an audience camera. A yes/no flag, published to demand partners alongside the face.
Screen ID	A demand partner’s own identifier for this face, so the partner can be answered in its own terms when it calls back. Free text.
Legal entity	Which of the organization’s billing identities this face belongs to. Chosen from the organization’s legal entities.

Setting

What it is

Format

The commercial format label — billboard, supersite, cityboard, media facade and so on. Chosen from the list the deployment defines.

Camera

Whether this face has an audience camera. A yes/no flag, published to demand partners alongside the face.

Screen ID

A demand partner’s own identifier for this face, so the partner can be answered in its own terms when it calls back. Free text.

Legal entity

Which of the organization’s billing identities this face belongs to. Chosen from the organization’s legal entities.

Saving is refused if the chosen legal entity does not belong to this organization, or belongs to it but is not active. Clearing the legal entity detaches the face.

The format list is the same for every organization on the instance. A new face is given a format the first time it appears, and after that the value is a stored setting like any other.

Whether an edit survives a run

Three of the four survive a synchronization run on every integration. Format and the camera flag depend on where the organization’s inventory comes from.

Setting	Survives a run	Detail
Format	On most integrations	On the CS Play pull, the spreadsheet import and SpinetiX an edited format stays edited. On CubicVision and inventory drawn from another exchange the format is taken from the source on every run, so an edit there lasts until the next run.
Camera	On most integrations	Kept on the content-management integrations. On inventory drawn from another exchange the source’s value is written on every run, so an edit there lasts until the next run.
Screen ID	Everywhere	Set only by the face edit form.
Legal entity	Everywhere	Changed only by the face edit form.

Setting

Survives a run

Detail

Format

On most integrations

On the CS Play pull, the spreadsheet import and SpinetiX an edited format stays edited. On CubicVision and inventory drawn from another exchange the format is taken from the source on every run, so an edit there lasts until the next run.

Camera

On most integrations

Kept on the content-management integrations. On inventory drawn from another exchange the source’s value is written on every run, so an edit there lasts until the next run.

Screen ID

Everywhere

Set only by the face edit form.

Legal entity

Everywhere

Changed only by the face edit form.

If your organization’s inventory comes from CubicVision or from an exchange, treat format as source-owned and fix it at the source. An edit made here lasts until the next hourly run and then reverts.

What the source owns

Everything below is replaced from the source whenever it differs, with no way to change it in CityScreen Context.

On the screen: Title, street address, coordinates, logical resolution, physical resolution, physical size, indoor or outdoor placement, static or mobile installation kind, description, downtime, photographs. A screen has no edit form.
On the face: Name, GID, external identifier, resolution, position on the screen, operating schedule, photographs, slot type and slot reserves, duration limits, side label, opportunity-to-see and gross-rating-point figures, angle, level, height, altitude, azimuth, tags, custom fields.
Derived by the platform: The time zone, computed from the screen’s coordinates — see Time zones and schedules. The nearest postal address, updated when the coordinates change.

Activation, likewise, is normally not an operator decision. Activation and archiving explains when it is.

Things that are editable but are not on this form

Two more per-face surfaces are the operator’s, and neither is touched by a synchronization run. They are saved separately from the four settings above.

Technical requirements: Free text describing what creatives this face accepts, kept on its own tab. Written by owner, admin and manager employees. Read by people, not enforced by the platform — see Technical requirements.
Bid settings: The per-face part of the floor price — see Bid floors.

Where inventory comes from

A face exists because a synchronization run or a file import created it, and it leaves the sellable catalog by being deactivated.

If a face is missing, the fix is at the source and then a synchronization run — see Synchronization.