Feature

Section-aware governance

Governance in CiteLoop keeps shared infrastructure usable across desks and teams. Sections scope data visibility, roles control actions, and ACLs restrict story and POV access where needed.

Book product demo See comparison

Features/Section-aware governance

What it is

Larger organizations run multiple desks, campaigns, or business units on one platform. Section-aware governance limits which stories, participants, send lists, clips, and graphics templates an operator sees based on active section context. Role permissions further constrain what actions are available.

Section selector filters lists across Engage pages
Stories can carry section assignment
Shared graphics templates can be scoped to selected sections
Story and POV ACL capabilities on story cards
Focused vs expert page modes hide or expose advanced controls

Who uses it

Newsroom groups with multiple desks use sections to avoid cross-desk noise. Community organizations with regional teams use the same mechanism for campaign isolation. Administrators manage shared templates and defaults.

Desk editors: work inside their section without global clutter
Administrators: publish shared templates and defaults
Multi-brand setups: separate participant pools and house styles

What you control

Governance is configured through organizational setup, not improvised per send.

Which section an operator is working in
Section assignment on stories
Shared vs personal graphics templates and section visibility
Access levels on stories where ACL is enabled
Expert-only filters (section filter, marked POVs, advanced send options)

How it differs from one shared inbox for everyone

An unscoped shared tool mixes unrelated stories, templates, and participant pools. CiteLoop uses sections and roles so teams collaborate on common infrastructure without losing local control.

Participant and story records respect section context
Graphics templates can be org-wide, section-scoped, or personal
Page mode reduces UI complexity for operators who do not need expert controls
ACL on stories supports tighter edit access where required

Workflow steps

What happens from link creation to a reply in the inbox.

Step 1
Assign organizational sections
Administrators define sections that map to desks, regions, or brands in the organization's CiteLoop setup.
Step 2
Operators select active section
Editors choose a section in the sidebar filter. Lists on Stories, POVs, POV panel, Create, and Graphics respect that scope in expert mode.
Step 3
Scope stories and templates
Stories carry section metadata. Shared graphics templates can be limited to selected sections; personal templates stay with individual users.
Step 4
Apply access controls where needed
Story cards expose ACL and access level controls for tighter edit permissions on sensitive work.
Step 5
Run outreach and production inside scope
Outreach, inbox triage, and rendering proceed within the active section so outputs and participant pools stay coherent for that team.

Product screenshots

Section-aware workspace. Section-aware workspace and access. — Section-aware workspace and access.

Newsroom governance. Keep desk-level workflows scoped and coordinated. — Keep desk-level workflows scoped and coordinated.

Common questions

What is a section in CiteLoop?

A section is an organizational scope—typically a desk, team, or business unit—that filters which records and templates an operator works with when section filtering is enabled.

Does every user see all participants?

Not when section scoping is in use. Participant and story visibility follows section assignment and the operator's active section filter.

What is the difference between focused and expert mode?

Focused mode keeps primary workflows visible and hides infrequent controls such as advanced filters and some expert-only send options. Expert mode exposes the full surface, including section filters and additional POV list filters.

Can graphics templates be shared across sections?

Yes. Shared templates can be visible to everyone or limited to selected sections. Editors can copy shared templates into personal templates for local adjustments.

Does governance replace editorial policy?

No. It provides technical scoping and access control. Editorial standards and approval workflows remain the team's responsibility.

Related terms

Definitions used on this page.

Story

The higher-level container that groups one or more POVs around a shared editorial or campaign objective.

Read in glossary

Participant

A contributor profile that can represent an expert, citizen, audience member, or campaign respondent.

Read in glossary