Skip to main content

Host Actions

This chapter is the host-side companion to Space Actions. The participant chapter explains what an Action looks like to someone who shows up to engage; this one walks you, the host, through creating and editing each Action type.

Creating an Action

Open your Space's actions page at /spaces/:space_id/actions and click the + Create affordance on the action carousel — the modal that opens is the entry point for every Action you'll author.

The modal asks one question first: what kind of Action? You pick from four tiles:

TileWhat it makes
PollA quick vote — single choice, multi-select, subjective text, or a linear scale.
QuizScored questions with a passing threshold.
DiscussionA host prompt with rich-text replies.
Follow FollowA campaign that asks participants to follow a curated set of accounts.

Pick a tile, see a live Preview of the empty card on the right, then click Create. Ratel takes you straight to the new Action's editor URL where you fill in the rest.

About Meets. The fifth Action type — Meet (a scheduled event with RSVP) — exists in the platform and has its own viewer at /spaces/:space_id/actions/meets/:meet_id, but a host editor entry point is (Coming soon). Today Meets are typically created via the MCP API (create_meet tool) and then surface in the participant carousel like any other Action.

How an editor URL works

Every Action editor lives under a stable URL pattern:

TypeURL
Discussion/spaces/:space_id/actions/discussions/:discussion_id/edit
Poll/spaces/:space_id/actions/polls/:poll_id (admin view)
Quiz/spaces/:space_id/actions/quizzes/:quiz_id (admin view)
Follow/spaces/:space_id/actions/follows/:follow_id (admin view)
Meet/spaces/:space_id/actions/meets/:meet_id (admin view)

Discussions have a dedicated /edit URL; Poll / Quiz / Follow / Meet share their URL between admin and participant views — Ratel detects whether you're an admin and flips the page into editor mode for those four. Participants visiting the URL see the participation card; you see the editor.

Edits autosave with a debounce; the Save button in the footer flushes pending saves and fires a Saved toast. There is no separate "Publish" button — saving and publishing are the same gesture.

Common Configuration

Every editor is split into a Content card on top and a Configuration card below. The Configuration card has the same set of sections across all four Action types:

SectionWhat you set
ScheduleStarts at and Ends at date-times. Outside this window the Action isn't active.
Participation & RewardsThe reward in Credits (CR) drawn from the Space's Incentive Pool. Credits convert to participant points on completion.
Dependency ActionsOther Actions in the Space a participant must complete first to unlock this one.
StatusToggle the Action between draft / live / closed.
Danger zoneDelete the Action. Submissions/responses go with it; rewards already paid are not refunded.

Discussions add a Moderation section (assigning who can hide replies); Polls add a Voting rules section (see below).

Discussion editor

URL: /spaces/:space_id/actions/discussions/:discussion_id/edit

The Content card holds:

  • Title — what people see at the top of the discussion card.
  • Description / body — Markdown-supported rich text. This is the prompt participants reply to.
  • Attachments — drag-and-drop PDF / PNG / JPG up to 25 MB each.

The Configuration card adds Moderation alongside the common sections. Use Moderation to set who can hide off-topic replies once the discussion is live.

Poll editor

URL: /spaces/:space_id/actions/polls/:poll_id

The Content card holds:

  • Title — the headline of the poll.
  • Questions — between 1 and 20 questions. Each question chooses one of four types:
    • Single — one option per question (radio).
    • Multi — multiple options selectable (checkbox).
    • Subjective — free-text response with an optional inline hint shown above the input.
    • Linear — a numeric scale with min / max bounds (1–5, 0–10, etc.).
  • Allow "Other" option per question — adds a free-text "Other" choice next to the fixed options.

The Configuration card adds Voting rules alongside the common sections:

  • Allow response editing — when on, participants can update their answers while the poll is open. Off makes responses final on submit.
  • Encrypted upload — when on, vote results are encrypted and stored on-chain; responses cannot be edited after submission. Use this for high-stakes votes where auditability matters.

Quiz editor

URL: /spaces/:space_id/actions/quizzes/:quiz_id

The Content card holds:

  • Title and Description — the framing shown before participants start.
  • Questions — between 3 and 20 questions, each Single or Multi choice with a marked correct answer.
  • Pass Score — minimum score (out of total questions) to clear the quiz.
  • Retry Count — how many attempts each participant gets.
  • Survey Time — total time allowed per attempt.
  • Attachments — reference materials participants can consult: PDF / PNG / JPG up to 25 MB each.

Pass and the reward unlocks; fail and (if Retry Count allows) the participant can try again.

Follow Follow editor

URL: /spaces/:space_id/actions/follows/:follow_id

The Targets card holds:

  • Title — what the campaign is called.
  • Targets — between 1 and 20 user accounts the participant should follow. Each target is rendered as an inline row in the participant view with a Follow button right there.

The Configuration card has the common sections only — Schedule, Participation & Rewards, Dependencies, Status, Danger zone.

Meet editor (Coming soon)

URL: /spaces/:space_id/actions/meets/:meet_id (admin view)

A scheduled event — livestream, video call, workshop, in-person gathering. The participant view at this URL is live, but a host editor entry point in the create-modal is (Coming soon). Today, hosts who need a Meet can create one via the MCP API (create_meet tool — see Connect AI).

Tips

  • Save your reward budget for the right Actions. Credits come out of the Space's Incentive Pool. A Quiz for onboarding can be reward-free; the deep Discussion that anchors your final Report is where Credits earn their keep.
  • Use Dependencies to build a sequence. A common pattern: a quick Sample Poll → a deep Final Poll. Make the Final depend on the Sample so participants warm up before the headline question.
  • Test with the participant view. Open the same URL in a private window or a different browser session — that's exactly what your participants see. The admin / participant flip is automatic.

What's next