Skip to main content

Requests

A Request is the universal unit of work in Vidiking — a ticket, like a Jira issue, with a human-readable reference such as VID-2026-000001. Everything in Content Operations hangs off Requests: workflows attach to them, sprints contain them, the Gantt draws them as bars, and AI jobs are spawned by them.

Open Manage → Requests (/requests) to work with them.

What a Request holds​

FieldMeaning
RefAuto-generated, unique per organisation, e.g. VID-2026-000001.
TypeThe kind of work — e.g. VIDEO, SOCIAL, MARKETING_CAMPAIGN, CUSTOM.
PriorityLOW · MEDIUM · HIGH · URGENT.
StatusBACKLOG → TODO → IN_PROGRESS → REVIEW → DONE.
AssigneeThe person responsible.
Start / Due datesDrive the Gantt timeline automatically.
Story pointsOptional estimate, used for sprint burndown.
Parent / childrenA request decomposes into layer children (see below).

Who sees what​

  • Managers (MANAGER+ or the team owner) see all requests in the organisation.
  • Everyone else sees only the requests assigned to them. This is automatic and enforced everywhere — listing, viewing, standups and generation.

So a CREATOR opening the Requests page sees their own queue; a MANAGER sees the whole board.

Create a request​

  1. On the Requests page click New Request (managers only).
  2. Set the title, type, priority, assignee, start/due dates and (optionally) story points.
  3. Save. Vidiking assigns the next ref for your organisation.

Decompose into layers​

A finished video is made of parts — script, visuals, voiceover, music. In Vidiking these are child requests, each a layer you can assign independently. From a request's detail panel, use Decompose to add layers:

Layer kindTypical content
TEXTScript / copy
IMAGEStills, thumbnails, backgrounds
VIDEOVideo clips
MUSICBackground track
VOICEOVERNarration

For each layer you choose a mode:

  • AI — the layer will be generated by an AI job (burns credits when run).
  • MANUAL — someone will upload or produce the asset by hand (no credit).

You can also set an assignee per layer, so different team members own different parts of the same video.

Run AI generation on a layer​

For any layer set to mode = AI, the detail panel shows a ⚡ Generate button. Pressing it captures the generation parameters and fires an AI job through Vidiking's existing job system. This is the moment credits are spent — and the only moment.

The Gate applies here: you must be verified and have a positive balance. If not, generation is refused and no job is created and no credit is charged.

When the job completes, its output asset is linked back to the request, the layer is marked done, the request's progress rolls up, and a standup entry is recorded automatically.

Credits, precisely

Generating an image, video, voiceover, script, or running a final render burns credits. Creating the request, decomposing it, assigning it, and tracking it are all free. See Credits & Billing.

Daily standups​

Each request has a standup control: a progress slider, a note, and a blockers field. Posting a standup:

  • records an immutable StandupLog entry (date, progress %, note, blockers),
  • updates the request's progress,
  • notifies the manager when the request crosses a milestone.

The history of standups is shown on the request, giving a running diary of how the work progressed — which also feeds the sprint burndown and the AI Project Manager.

Assembly & completion​

When all of a video's layer-children are done, the parent request is ready for final assembly in the Studio editor, where the layers are pulled together and rendered. If the request has a Workflow attached, progression through review and publish stages is handled there.

Next​