Accounts and access
Account type, permissions and creative credit serve different purposes.
Independent
A solo workspace with one seat. Choose Professional when you need to invite people into your workspace.
Professional
A workspace with five total seats, including its owner. Active members and pending invitations to new people use that allowance.
Studio
Production engagements start at $299 USD per month by agreement. Scope the project, team access, review and onboarding with DigiBridge.
Enterprise and API
Agree access across teams, review capacity and commercial terms for your organisation. Public record lookup is documented below; additional API services require a separate agreed interface.
Owner and Admin
The workspace owner and workspace admins manage invitations. Admin permissions apply to the workspace; a project or asset invitation does not delegate management of other people.
Contributor
Contributor access allows work within the area granted in the invitation. A project or asset invitation limits that access to the named work.
Reviewer
Reviewer access is view only for the area granted. Being a verifier or reviewer by profession does not itself grant access to someone else’s projects.
Creative role or credit
Producer, editor, VFX artist, engineer or musician describes what the person contributed. Confirming that declaration is separate from access, identity verification and the review of the work.
Collaboration guide
Invite, confirm, then choose what to share.
1. Choose access
In Team, choose Contributor or Reviewer access and the workspace, project or asset it covers. The recipient uses their own account and completes the required identity check.
2. Confirm the contribution
Open the asset’s Contributors tab to review creative credits. The person managing the asset requests confirmation, and the contributor can confirm or decline their own declaration.
3. Prepare a selected version
Open project review and choose the eligible asset versions and public details. The saved selection remains private during review; later work is not added automatically.
Workspace seats count people with active or pending access, not the number of contribution records. Access covers the shared records in the selected area. Before sharing a project, check the exact versions, contributor credits and details in its preview.
Recording and review
Understand a warning before you respond.
Read the reason and evidence
Check the affected recording, activity and supporting evidence. The warning distinguishes a finding awaiting confirmation from a confirmed incident.
Add context or request review
Explain relevant circumstances and challenge a finding or assignment you believe is wrong. Corrections preserve the original history and update the resulting restrictions.
Keep uncertainty visible
AI suspicion, unsupported observations and recording gaps alone never count as strikes. Confirmation requires qualified evidence of a prohibited action; one continuous episode counts once.
Check publication eligibility
The first confirmed incident holds the affected version from publication. The third distinct confirmed incident makes the project ineligible for directory submission and publication.
Ordinary playback, keyframes, rendering, sequencing and musical automation follow the disclosed policy for the connected tool. They are assessed separately from software performing the contributor’s actions. These are the programme rules; the public v1 lookup API does not run the verification engine or return incident decisions.
Choose a workflow
Start from the user visible outcome.
Resolve a public record
Use a public verify ID or slug to request an approved preview response.
Render a trust aware preview
Show the asset and creator context while preserving preview, draft and false trust state fields.
Evaluate device contracts
Test pairing, event validation and revocation with an authorised test workspace using the device reference.
Guide 01
Build a public record lookup.
const code = encodeURIComponent(userInput.trim());
const response = await fetch(
"/api/verifier/v1/resolve?code=" + code,
{ method: "GET", headers: { Accept: "application/json" } }
);
if (response.status === 404) {
showUnavailableMessage();
return;
}
if (!response.ok) {
throw new Error("Verifier preview request failed");
}
const record = await response.json();
renderPublicPreview(record);Guide 02
Keep trust state language attached to the data.
Required presentation boundaries
- Display Public preview only near the record state
- Display Draft certificate preview near draft hashes
- Do not convert false trust flags into a verified badge
- Show detection or verification conclusions only when the response supplies them
Guide 03
Evaluate the device simulator as an API contract.
Pair
Create a 10 minute code, register a simulator device and retain the one time token locally.
Create and ingest
Start an asset session, generate canonical signed events and submit them in order.
Inspect and revoke
Review safe validation summaries, then revoke the device to block future ingestion.
Guide 04
A published selection is separate from ongoing private work.
Private workspace state
Projects, internal IDs, evidence, contributor contact data, raw events and device context remain inside access controlled routes.
Selected public record
The Verifier API reads the fields approved for an active public preview. Display the supplied status and version, rather than treating the private project as a live public feed.