POKA avatar logoPOKAv0.1

POKA Documentation

Secure Deliveries

Controlled client handoff flow with password protection, scoped access, and delivery lifecycle visibility.

Overview

Business operations hub for agencies, freelancers, and production teams.

  • Best suited for :

    • Media agencies sending campaign exports to clients and partners.
    • Freelancers delivering paid milestones and final output packages.
    • Production houses handing off masters, stems, and review cuts.
  • Delivery package options include :

    • Single-file deliveries for quick approvals.
    • Multi-file bundles for campaign or milestone handoff.
    • Folder-level deliveries for full project output sets.
  • Access control includes :

    • Recipient scope restrictions.
    • Optional password requirements.
    • Delivery validity and expiry settings.
    • Revocation or rotation when recipients change.
  • Tracking and operations include :

    • Open and download lifecycle visibility.
    • Resend and revision handoff process.
    • Archive and closeout records for audit context.

Step-by-step Flow

Campaign-Master-v12.zip1.8 GB
Social-Cutdowns-v4.zip650 MB

Select Final Assets

Select finalized project files from briefcase or storage.

Step 1 of 8

Limits

Operational Constraints

  • Recipient experience depends on settings configured at delivery creation time.
  • Incorrect access scope can cause either blocked clients or over-shared links.
  • Large file downloads remain dependent on recipient bandwidth and network stability.
  • Password-protected deliveries require recipients to handle credentials correctly.
  • Delivery link hygiene is still required; avoid forwarding outside intended audience.
  • Lifecycle tracking reflects access events, not legal acceptance of deliverables.

Notes

Recommended Practices

  • Media agencies: Name deliveries by client, campaign, and version so account managers can track handoffs quickly.
  • Freelancers: Use password-protected deliveries for paid milestones and final masters.
  • Production houses: Assign one delivery owner per project to keep recipient communication clean.
  • Client ops teams: Document re-delivery policy so revisions and re-exports stay consistent.

Workflow Diagram

Secure DeliveriesRoot
Package Preparation

File Selection

Pick approved project files ready for client release.

Bundle Validation

Verify file count, naming, and version consistency.

Version Lock

Lock final output set before distribution.

Access Policy

Recipient Scope

Restrict access to intended recipients only.

Password Rules

Apply passwords for sensitive deliverables.

Expiry Windows

Set validity windows for safer link usage.

Distribution and Monitoring

Link Generation

Create shareable delivery access link.

Client Handoff

Send delivery details through approved communication path.

Open and Download Status

Track recipient access and completion signals.

Archive and Closeout

Close delivery lifecycle and preserve audit context.