RSVP for Confluence Cloud - User manual

RSVP for Confluence Cloud adds an interactive RSVP macro to Confluence Cloud pages. Use it for meetings, events, training sessions, internal activities, and any page where people need to register attendance directly in Confluence.

Last reviewed: 2026-06-01

Key features

• Add an RSVP macro to any Confluence Cloud page.

• Collect attendee name, email address, response status, comments, and RSVP timestamp.

• Support response statuses: Attending, Declined, and Waitlisted.

• Configure capacity limits, including blocking new attending responses or allowing a waitlist.

• Add custom RSVP questions with optional required answers.

• Show responses as standard cards or compact rows.

• Optionally enable response search and status filters.

• Let users edit or remove their own RSVP.

• Let organizers manage responses, export CSV data, check attendees in, use Rovo assistance, and notify selected respondent groups.

• Show a page-level RSVP byline summary in the Confluence title metadata row when a page contains RSVP macros.

Getting started

1. Open the Confluence page where you want to collect RSVPs.

2. Click Edit.

3. Insert the RSVP macro from the macro browser, or type /RSVP and select the RSVP macro.

4. Publish the page.

The macro has useful defaults, so it can be inserted and published without opening settings first. To customize it, edit the macro and open RSVP settings.

Page byline summary

When a Confluence page contains one or more RSVP macros, RSVP adds a compact byline item to the page title metadata row.

• The row shows a compact status such as RSVP: 12 attending, RSVP: 12 / 20 attending, or RSVPs: 2 events.

• Selecting the byline opens a small summary popup with response totals, capacity state, and event summaries.

• For privacy, the popup does not show attendee names, email addresses, comments, or custom question answers.

• After adding or removing the last RSVP macro, reload the page if the byline visibility has not refreshed yet.

Configure the RSVP macro

Open the macro settings to configure the event and display behavior.

Basic settings

• Title: the heading shown above the RSVP macro.

• Description: optional supporting text shown below the title.

• Content width: the macro width, such as 400, 600px, 50%, or another valid CSS width.

• Content alignment: left, center, or right.

• Attendee display: standard cards or compact rows.

• Reply button value: custom text for the primary response button.

• Users must be logged in to reply: controls whether the current Confluence identity is required for replies.

• Unique identifier: use only when one page needs multiple independent RSVP macros or when preserving a legacy RSVP identity.

Capacity and response display

• Maximum attendees sets the number of attending spots.

• When maximum attendees is reached controls whether new attending responses are blocked or added to a waitlist.

• Response count display can show a status breakdown or a simple respondent count.

• Show declined count and Show waitlist count control which status totals appear when using the status breakdown display.

• Show row status badges controls whether each response row shows its status.

• Response filters controls who can see the search and status filter controls:

  • Hidden

  • Show to attendees

  • Show to signed-in Confluence users

  • Show to organizers and admins

Custom RSVP questions

Use the Custom questions tab in RSVP settings to ask for extra information when people respond.

Supported question types:

• Short text

• Long text

• Single select

• Yes / no

Question behavior:

• Up to 5 custom questions are supported.

• Single-select questions can have up to 10 options.

• Questions can be required.

• Questions can include help text.

• Questions can be reordered or removed.

Answer display options:

• Icon indicator shows whether a response has answers without showing all values inline.

• Inline answers shows answers directly in the response list.

Answer visibility options:

• Page viewers: page viewers can see answers.

• Managers only: only organizers and admins can see answers in the macro view.

• Export / edit only: answers are hidden in the macro view but remain available when editing a response and in CSV export for authorized users.

Responding to an RSVP

When a viewer opens a page with an RSVP macro, they can select the response button and submit a response.

The RSVP form can include:

• Name

• Email address

• Status: Attending, Declined, or Waitlisted

• Comment

• Custom question answers, when configured

For logged-in Confluence users, the form can prefill profile details. Required custom questions must be answered before the response can be saved.

If a maximum attendee limit is configured:

• Attending responses count toward capacity.

• Declined responses do not count toward capacity.

• Waitlisted responses are available only when the macro is configured to allow a waitlist.

Managing your own RSVP

Users can update or remove their own RSVP from the response list.

Depending on the stored response identity, the action menu may show:

• Edit my RSVP

• Remove my RSVP

Editing lets the user update their name, email, status, comment, and custom question answers.

Organizer and admin actions

Page managers, page authors, and Confluence admins have organizer-level controls.

Organizers can:

• Edit another attendee's response.

• Remove another attendee's response.

• Mark attendees as checked in, or undo check-in.

• Export responses to CSV.

• Open Ask Rovo for RSVP summaries and drafting help.

• Open Notify to prepare and send respondent notifications.

Normal attendees can manage only their own RSVP.

Viewing responses

Responses appear below the RSVP form.

Depending on macro settings, responses may appear as:

• Standard cards

• Compact rows

The response list can show:

• Attendee name

• Email/contact details, when available

• Comment

• Status badge

• Check-in badge

• Custom question answer indicators or inline answers

If response filters are enabled, viewers can search responses by name or email and filter by status.

Exporting responses

Organizers can select the export icon in the macro header to download a CSV file.

The CSV can include:

• Full name

• Email

• Comment

• RSVP timestamp

• Status

• Custom question answers

• Checked-in timestamp

• Checked-in-by account ID

• Attendee account ID

• Attendee profile URL

Export is disabled when the app license is inactive or when the macro is temporarily blocked by migration/import state.

Ask Rovo

The Ask Rovo action opens the bundled RSVP Organizer agent with context from the RSVP macro.

Rovo can help organizers:

• Summarize the current RSVP event.

• Check capacity risk and remaining spots.

• Summarize attendee comments.

• Draft a general RSVP reminder.

• Draft attendee follow-up copy.

• Identify missing custom question answers.

Rovo is read-only. It does not create, update, remove, email, notify, or send anything.

If a Confluence page contains multiple RSVP macros, Rovo may ask which RSVP event to use. Choose the exact macro title, or open Ask Rovo from the specific RSVP macro header.

Notify respondents

The Notify action is available only to page managers, page authors, and Confluence admins.

Notify lets organizers prepare a Confluence comment notification for selected RSVP audiences. Before sending, the macro shows a preview of recipients and requires explicit confirmation.

Supported audiences:

• Attending

• Declined

• Missing a custom question answer

• Non-respondents, when enough information is available

The preview shows:

• Direct recipients with Confluence account IDs

• Manual follow-up rows for respondents without account IDs

• Selected response count

• Missing question-answer counts, when relevant

• Draft notification message

Notifications are sent through a Confluence footer comment with mention recipients. If the same audience and message were sent recently, the macro asks for an explicit send-again confirmation.

Licensing and migration messages

If the app license is inactive, existing responses remain visible, but new sign-ups and mutation actions are disabled until the license is restored.

During migration or import, a macro may show a banner that historical RSVP data has not been imported yet. When this happens, the macro prevents unsafe changes until the data is verified or imported.

Data storage and privacy

RSVP for Confluence Cloud stores RSVP data in Atlassian Forge SQL.

Stored RSVP data can include:

• Confluence page ID

• RSVP macro identity

• Name

• Email address

• Comment

• RSVP timestamp

• Response status

• Custom question answers

• Check-in metadata

• Confluence account ID and profile metadata when available

Data is scoped to the Confluence page and RSVP macro identity. There is no global attendee directory in the user-facing macro.

Support

For help, contact support@krosoft.nl or visit the Krosoft Support Portal.