Glossary
Use this glossary to understand how CiteLoop structures stories, contributors, outreach, governance, and output workflows.
These definitions match the product model used across the website and public workflow documentation.
A specific angle inside one story or campaign, with its own question set, audience, and outreach message.
A POV is the operational unit that lets teams collect different kinds of perspectives without flattening everything into one generic prompt.
Why it matters
POVs help teams structure broader sourcing and avoid treating every story or campaign as a single undifferentiated callout.
Full term pageThe higher-level container that groups one or more POVs around a shared editorial or campaign objective.
A story provides the shared context for multiple POVs, keeping related sourcing and outputs tied together.
Why it matters
Stories let teams coordinate complex work without losing the difference between angles.
Full term pageA contributor profile that can represent an expert, citizen, audience member, or campaign respondent.
Participants can carry tags, interests, expertise, states, and settings that make outreach reusable over time.
Why it matters
Participants turn sourcing from one-off contact hunting into operational infrastructure.
Full term pageA managed access-link flow used for public or semi-public registrations and callouts.
Open invitations let teams launch broader participation workflows with reviewable intake instead of dumping everything into a generic form endpoint.
Why it matters
They support scale without giving up workflow control.
Full term pageScoping stories, participants, templates, and settings by organizational section or team.
Section-aware governance helps larger organizations coordinate multiple desks, campaigns, or business units without turning the platform into one global pool.
Why it matters
Governance is often the difference between a usable shared platform and an abandoned one.
Full term pageAn asynchronous background job that turns prepared clips and settings into a deliverable output.
Render jobs let teams keep working while media outputs process in the background.
Why it matters
They reduce bottlenecks between curation and distribution.
Full term pageUsing language-aware templates and message variants during participant communication.
Multilingual outreach keeps source communication and campaign communication usable across multiple audience languages.
Why it matters
Language support makes broader participation operationally realistic, not theoretical.
Full term page