By default the drag updates only the local Review state column SleekView adds. If you enable Crowdsignal write-back in the connection settings, the drag also pushes a custom tag to the response through the Crowdsignal API so both systems show consistent state and downstream exports include the tag.

Yes. Any single-choice or multi-choice answer on the survey, poll, or quiz is a valid grouping axis. You can also group by score band for NPS or rating questions by defining buckets, which is useful for segmenting respondents into detractor, passive, and promoter columns automatically.

The default refresh interval is fifteen minutes and runs through WP Cron. The interval is configurable in SleekView settings and a manual sync button is also available. The mirror table is keyed by Crowdsignal response ID so re-running sync never duplicates rows already imported into the database.

Yes. Polls and quizzes use the same Crowdsignal API endpoints with a different content type. SleekView treats them identically and you can build boards on top of poll responses grouped by a moderation Stage column or quiz responses grouped by score band for reviewer follow-up.

Yes. Boards are saved as named views and each view scopes to specific WordPress roles. Research can see a coding board, customer success can see a detractor follow-up board, and marketing can see a promoter quote board, all reading from the same mirrored Crowdsignal response set.

If the Crowdsignal survey collects respondent name, email, or any other identifying field, those values land in the mirror table and can be rendered on card faces. Anonymous surveys keep respondents anonymous on the board, since the mirror simply reflects whatever Crowdsignal stored.

Yes. SleekView batches response fetches into pages of fifty and respects the standard Crowdsignal API rate limits and pagination tokens. Large surveys with thousands of responses sync in the background without blocking the admin and resume from the last cursor on the next scheduled run.

Archived responses are filtered out of every default board because the Archived column is excluded by default in board configuration. The responses remain in the local mirror so an archive review board can be built that flips that filter to surface only archived responses for audit or recovery.