Publishing Requirements

Publishing technical requirements means writing text, and optionally attaching documents, in the client cabinet. What is saved is what the next demand partner request returns.

This page is for the owner, admin and manager of a screen operator’s organization. A viewer can read both surfaces but cannot change either.

Writing the organization requirements

The organization note lives in the Inventory section of the client cabinet, on the Technical requirements tab next to the inventory list.

Publishing the organization note

  1. Open Inventory and select the Technical requirements tab.

  2. Click Edit. The rich-text editor opens on the current text, and the document area below it becomes editable.

  3. Write the text. It is ordinary formatted prose — headings, lists, links — and there is no length limit.

  4. Click Save.

The Edit button appears for owner, admin and manager. Saving replaces the whole note.

Creating, changing or deleting the organization note is recorded in the organization’s audit log. See Audit.

Attaching documents

While the note is in edit mode, a drop zone appears under the document list. Drop PDF files onto it, or click it to pick files.

Uploads are independent of the text. A file is uploaded as soon as it is queued, and the delete icon next to a listed document removes that document immediately, without waiting for Save. A document’s title is taken from the uploaded file name.

What is accepted

Only PDF files are accepted. The quotas below are per organization and count only these documents.

Limit Value Applies to

Documents per organization

10

Further uploads are refused.

Size of one document

20 MB

Larger files are refused.

Total size of all documents

100 MB

The sum of every attached document. An upload that would exceed the total is refused.

A file that fails a check is marked in the drop zone with the reason, and the queue moves on to the next one.

Removing what you published

Documents are removed one at a time, with the delete icon beside each one in the list. Removing a document deletes the stored file with it, and the link that was handed to partners stops working.

The text is removed by editing it to nothing and saving. A partner asking for the note then receives an empty text. An organization that wants partners to see nothing at all removes the documents as well.

Writing a face’s requirements

Each face has its own Technical requirements tab, alongside Info and the face’s bid settings.

Publishing a face note

  1. Open Inventory, then the face.

  2. Select the Technical requirements tab.

  3. Click Edit, write the text, and click Save.

The Edit button is hidden for viewer and for archived faces. Saving is accepted for owner, admin and manager.

Inventory synchronization leaves the face note alone, so it survives the runs that overwrite most of the rest of the face. See What you can edit.

Who can see what

Audience What they see

Employees of the organization

Both surfaces, in the client cabinet. Every employee role can read them, viewer included.

The platform operator

A face’s note, read-only.

Demand partners on the platform’s own SSP protocol

The organization note and the titles and links of its documents. Partners integrated by other means are refused this request.

Demand partners buying through the automated guaranteed path

The organization note and its documents as owner info, and each face’s note inside the automated guaranteed inventory feed.

Anyone holding a document link

The document itself, without signing in.
A document link works for anyone who has it. Attach only material you are willing to publish.

Changing what is published

A save takes effect on the next request a partner makes. No partner is told that the text changed, so a buyer working from a copy keeps working from the copy until it asks again.

Changing or deleting either surface leaves existing work exactly as it is. Creatives already approved stay approved, campaigns already running keep running, and no review is reopened. How they are enforced explains why, and what to do instead when requirements really change.

Related pages