Use cases
Choose the path for Users, Communities, Creators, or Sponsors and move directly to the workflow that matches your goal.
ZYNC connects a clear real-world action to proof, a decision, and a defined reward or report. The implemented roles and the Planned Creator workflow share one program lifecycle; choose the role closest to what you want to accomplish.
Users
Who it is for: people discovering Spaces and Missions, completing an action, and following the result as Members.
Problem: opportunities, proof requests, and rewards can be hard to judge before committing.
Main outcome: understand the complete path from finding a relevant Mission to seeing its verification and reward state.
Communities
Who it is for: organizers, Mission designers, reviewers, moderators, and partnership teams operating a Space.
Problem: participation becomes difficult to sustain when actions, proof rules, team access, and rewards are managed separately.
Main outcome: operate Missions with clear terms, consistent review, repeat participation, and accountable Sponsor work.
Creators · Planned
Who it is for: people who publish to an audience of their own and want funded programs worth putting their name on.
Problem: a brief that names compensation but not the disclosure duty, the qualifying action, or the correction window leaves the Creator carrying unstated risk.
Main outcome: understand the planned path for accepting a program on written terms, publishing attributable distribution, and reconciling its report and any program-defined compensation.
Sponsors
Who it is for: brands and organizations funding community outcomes.
Problem: attention metrics do not show whether a defined action happened or what qualified for a reward.
Main outcome: connect funding to agreed Missions, verification rules, and reports that keep limitations and exceptions visible.
New to the product model? Read what ZYNC is. For a capability-by-capability index, use the feature directory.