Draft, schedule, close and archive actions

An action’s status controls where it is in its working life. Drafts let signed-in creators prepare a request without inviting responses. Scheduling sets a future publishing time. Published actions can accept responses while their deadline remains open. Paused and closed actions stop new input for different practical reasons, and archived actions move out of active work. Moderation approval can add another publishing step.

Prepare a draft

Sign in and choose Draft in the builder’s publishing controls. Review the title, visibility, options and related link before publishing. A draft is not a substitute for a confidential workspace: the underlying audience still matters when it is published. Keep secrets and unnecessary personal records out of drafts as well as public pages. A response deadline and a publishing time serve different purposes. If you schedule an action, check that the response window still makes sense when it becomes available. Scheduled work depends on the site’s job runner; administrators should configure real hosting cron so a low-traffic period does not delay due jobs.

Publish and moderate

Publish when the wording is ready and the intended audience is correct. If the administrator requires moderation, the action enters a pending state until approved. Sending a URL before approval does not grant access or bypass moderation. Review the final live page before distributing the invitation widely. Editing important content can require moderation again, depending on the site’s settings. If you need to change the meaning of an option after responses arrived, duplicate the action and explain the new request instead. Preserving responses is more important than keeping the same URL for a materially different decision.

Pause, close or archive

Pause when a temporary problem makes additional responses unhelpful. Close when the response window is finished and the organizer is ready to act on the recorded result. Approved closed actions retain readable results for authorized viewers, but they do not accept new responses. A deadline can also end participation even if the page still displays the action. Archive work that no longer belongs in the active portfolio. Archiving affects active-action capacity; it is not necessarily equivalent to deleting all retained information. If an erasure request is needed, use the privacy process and consider any separate records the organization keeps. Do not represent an archived screen as proof that external obligations were cancelled.

Check before reopening or deleting

Reopening may change the result on which other people have already acted. Tell the group what changed and set a clear new deadline. If a venue booking, purchase or payment already happened elsewhere, a platform status change does not reverse it. Handle those obligations through their real provider. Deletion is a creator or administrator operation and should be deliberate. Team editors can have editing rights without having the owner’s deletion right. Before deleting, consider whether a result or task handover is still needed. Never export or retain participant data merely to evade an authorized privacy request.

Continue with related help

• Accessible participation and keyboard controls
• Contact support and track a useful request
• Use the local help assistant effectively
• Create your first action

Search the help center · Current plans and limits · Contact support

Still need a hand?

The site assistant can find related guides. For an account-specific issue, use the support form and include the page URL and exact error, without passwords or payment details.

Contact support ↗