Review with context. Act with a record.

Start of shift

Confirm the server and the current state.

1. Sign in through Discord

   Input: Open the moderator portal, select Continue with Discord, and approve the identity prompt.

   Expected result: The portal returns to Home. It never asks you to type your Discord password into Time Capsule. Its persisted session remains active across normal restarts until Discord invalidates authorization, you sign out, or security revokes it.

2. Select the server

   Input: Use the server switcher and choose the server for this moderation shift.

   Expected result: The portal rechecks authorization and displays that server’s name and bot state. If it is missing, ask an owner to review Manage Server or the configured Time Capsule management roles.

3. Read Home before changing anything

   Input: Review the summary and any items needing attention.

   Expected result: You have a current handoff view of capsule and delivery state before taking a staff action.

Discord moderation

Restrict bot access with a clear reason.

These commands require the server’s moderation_controls feature to be enabled and the caller to be the server owner, hold Manage Server, or hold a configured Time Capsule management role.

1. Choose the correct target method

   Input: Use /timecapsule ban when you know the member. Use /timecapsule ban-message when you have a capsule code, Discord message link, or raw Discord message ID and need Time Capsule to resolve its sender.

   Expected result: Discord displays the matching required and optional fields before you send the command.

2. Provide the member, reason, and optional duration

   /timecapsule ban user:@MEMBER reason:REASON duration:7d Copy example

   Input: Select the user, enter a factual reason up to 300 characters, and optionally enter a duration using 30m, 12h, 7d, 4w, 6mo, 1y, or forever. Review the target before sending.

   Expected result: The user is prevented from ordinary Time Capsule use in this server, receives the stated reason, and the action is written to the moderation audit.

3. Ban by capsule or message when necessary

   /timecapsule ban-message message:CAPSULE-CODE duration:12h reason:REASON Copy example

   Input: Enter the capsule code, full Discord message link, or raw Discord message ID. Duration and reason are optional for this command, but record a useful reason whenever possible.

   Expected result: Time Capsule resolves the sender, applies the server-local restriction, and records the outcome—or privately explains why the reference could not be used.

4. Restore access after review

   /timecapsule unban user:@MEMBER reason:APPEAL APPROVED Copy example

   Input: Select the user and enter the required unban reason, up to 300 characters.

   Expected result: The user can use Time Capsule again in this server, and the restoration is recorded in the moderation audit.

Portal review

Inspect the capsule before deciding.

1. Find the capsule

   Input: Open Capsules and use its search and filters. Use the capsule code, title, destination, or visible state available to you.

   Expected result: Matching server capsules appear; opening one loads its workspace.

2. Review all three workspace tabs

   Input: Read Overview for content and delivery, Automation for release workflows, and Activity for history.

   Expected result: You can distinguish content/destination concerns from automation or delivery failures and see recorded lifecycle activity before acting. The same capsule ID appears in the list, Overview, and Activity.

3. Check Safety context

   Input: Open Safety to review reports, current bans, reviewer alerts, moderation filters, crisis destinations, portal roles, and logging policy relevant to your access.

   Expected result: The action you take follows the selected server’s current safety configuration.

4. Record what another moderator needs

   Input: Keep the capsule code, action, reason, and timestamp in the server’s staff handoff process. Do not copy sensitive content into a public channel.

   Expected result: The next moderator can reproduce the decision without guessing or exposing private material.

Delivery recovery

Correct the dependency before retrying.

1. Read the visible state and last error

   Input: Open the affected capsule in Capsules, then inspect Overview, Content & delivery, and Activity.

   Expected result: You have the recorded failure state, destination, and timeline instead of relying on a member’s summary alone.

2. Check the Discord dependency

   Input: Confirm that the recipient, channel, thread, forum, bot access, and relevant role still exist and are allowed by Channel management.

   Expected result: You identify either a missing Discord object, a permission problem, a server policy block, or no obvious local cause. A deleted explicitly selected channel pauses for review and never falls back to the default channel.

3. Make the smallest safe correction

   Input: Restore the intended permission/dependency or select an allowed destination where the portal permits editing.

   Expected result: The capsule passes the corrected validation without weakening unrelated server policy.

4. Retry once and verify

   Input: Use the available retry/recovery control once, then refresh the capsule state and destination.

   Expected result: The state advances or the reveal appears once. If it fails again, stop retrying and preserve the new error/timestamp for support.

Server operations

Use the panel that owns the policy.

Member editing: When Allow members to edit their capsules is on, Edit in portal issues a short-lived, single-use link to a capsule-only page with no moderator navigation. Disabling the setting prevents new links and revokes active member-edit sessions.

For screen-by-screen controls, see the moderator portal guide.

Release recipes

Configure the condition before publishing.

The backup release time is optional but recommended, and new recipes leave it blank. Choose it deliberately when a fallback is appropriate.

• Role change: watch one member, all members already assigned a selected role, or anyone in the server.
• Invite use: release after role assignment, rules acceptance, or first message. Enable Ignore duplicate Discord join events when repeated join events should count only once.
• Milestone: optionally mention the member who matched the condition and select roles to mention.
• Recurring: choose multiple weekdays for a weekly schedule or multiple day numbers for a monthly one.
• Bot message: watch All channels or a multi-selected channel set. Numeric operators are enabled only while Text or number contains an integer or decimal; alphabetic text disables them.

A platform-disabled capsule type remains visible as IN MAINTENANCE, but it cannot be created or reconfigured until maintenance ends.

The main Recipes tab beside Vaults stores reusable Plus templates for capsule or vault settings and automation. Create one from an existing item, export one or a selected bundle, bulk import up to 100 recipes, and review the newest three retained versions. The Capsules bulk tool uses provided CSV, YAML, or JSON templates to import or export no more than 100 capsules per operation.

Vault operations · Plus

Confirm the shared release rule before moving capsules.

Vaults use the same event types as capsules and offer Server default—showing the current server timezone—or UTC. Published announcements offer Create capsule and Quick contribution. In Discord, the vault manager can move up to 25 eligible sealed capsules. In the portal, Add existing capsule moves one from a configured vault; to move one or several, select eligible rows in Capsules, choose Move to vault, then select an existing vault or continue to the new-vault form.

Created vaults remain in a table with name, channel, type, and type condition. Use Edit, Pause/Resume, View sub-capsules, or Delete. Each row names its state: Entries Closed, Capsules Locked, Entries Open, Capsules Locked, or Sealed, Capsule/Vault locked. The expanded sub-capsule view supports create, edit, pause/resume, inspect, and delete actions when the state permits.

Notifications and activity

Keep confirmations visible and changes reversible.

• One save or error notice floats at the top of the viewport, disappears automatically, and has an X on the right for immediate dismissal.
• The header bell opens notifications and recent activity. Mark all as read, dismiss one item, or dismiss all. Dismissal marks an item read so the unread count is not left behind.
• The help and activity drawers are mutually exclusive; the control selected most recently owns the open drawer.
• The full Activity page is searchable, filterable, and sortable. It shows actor, timestamp, change, prior value, new value, and relevant capsule, vault, or settings links.
• Undo is available only for the latest reversible change to each configuration setting. It reverts that last change; it is not version history.
• A changed settings form prompts before navigation. Choose Discard changes to leave or Stay on page to keep editing. Saving removes the prompt.

Escalation

Send support a reproducible case.

1. Open Contact support

   Input: In the portal, select the bottom-right Need help? control, then Contact support.

   Expected result: A secure form opens with category, summary, details, and optional reference. Your account, selected server, and current page are attached automatically.

2. Choose the category and describe one problem

   Input: Choose the closest category, enter a 4–120 character summary, explain what happened in 10–4000 characters, and add a capsule/request/message reference up to 120 characters when useful.

   Expected result: The form validates the required lengths and enables submission.

3. Submit and keep the receipt

   Input: Submit once.

   Expected result: The portal says Request [code] was sent securely to the support team. Save the code for follow-up.

For all categories, support-server onboarding, status updates, and private security reporting, use the Support & status guide.