Questions, answered

Click Get started, then use Proto to configure Digital Asset Management for your business. Begin with one project, an item, a file revision, a media version and the rights terms needed for a real release.

Each file revision links to a content item and records its own version, attachment, upload date and approving person. Keep corrected exports as distinct revisions so reviewers can identify the exact file they approved.

Yes. Each media version links to a content item and records its own version, file identity and review state. Usage rights can then be attached to the rendition they govern.

A rights agreement links to a content item and records the party, allowed uses, dates and contract. A usage right links to a media version and records the licensee, allowed use and interval.

The capture workflow resolves its linked content item and moves the submitted media version from draft to review. The review and approval decisions then use the linked file, item and rights context.

The Rights Manager checks coverage and approves the exact submitted file revision. The parent content item becomes approved through that review path. The Editor then handles publication.

The publication flow marks the approved item published, records its acknowledged publish time and closes linked production tasks.

When a linked production task reaches completed, its completion date is recorded and the project advances to delivered. Review the related content item separately for publication state.

Finance reviews a draft cost with its linked project and amount. An eligible cost can move to approved; paid remains a separate finance state.