Core documentation

A ready workspace for Core.

Sign in as the server owner or with Manage Server permission. Open Core, choose the correct server inside the app, and check its connection. Each app needs its own Discord installation consent.

New to Guildryx? Follow Getting started first

Follow the setup checklist

1. Open Core, find your server, and review the overview checklist. Each server has independent settings.
2. Review Discord member events, channel access, role placement, and published panels. Optional features can remain off.
3. Configure each feature, turn on its own switch, and save when ready. New modules are initially disabled; existing onboarding settings are preserved.

Personalize the welcome

1. Open your selected server’s Core workspace. Turn on Welcome messages, then choose a channel Core can view and send messages in.
2. Write a message of up to 1,000 characters. Personalize it with {member}, {username}, {server}, and {count}.
3. Review the sample and save. Send test posts one real message to the saved channel without notifying members.
4. The welcome applies to future human arrivals after any Discord membership screening. Existing members are not welcomed again when you save.

Assign safe starter roles

1. Enable Automatic roles and choose up to five ordinary member roles. Your account and Core need Manage Roles.
2. In Discord’s role list, move Core’s highest role above every role it should assign. Administrative or moderation roles cannot be granted automatically.
3. Save the setup. Core waits for membership screening before assigning roles to new arrivals.
4. Check Recent activity after a new member joins. This feature does not replace the roles of existing members.

Use embeds and welcome cards

1. In Welcome messages, choose Simple text, Branded embed, or Graphical welcome card.
2. For embeds and cards, choose the title, brand colour, and footer. The existing welcome message remains available as readable text.
3. Allow Embed Links in the welcome channel. Graphical cards also need Attach Files. Cards use the Discord avatar and fall back to initials if the avatar is unavailable.
4. For graphical cards, upload an optional PNG, JPEG, or WebP background up to 5 MB. The recommended resolution is 1000 × 340 pixels. Core crops other sizes to fit and shades the image for readable text. Uploading updates the preview without activating it. Restore default background clears the selection.
5. Save, then send a test to check the actual Discord result. The dashboard uses a sample preview; long card text may be shortened to fit.

Publish self-service roles

1. Open Self-service roles and create up to five branded panels. Choose a channel, embed title, instructions, accent colour, and optional footer. The live preview shows your message as you build it.
2. Choose Buttons or Dropdown for up to 25 roles, or Reactions for up to 20. Add a standard or custom Discord emoji, display label, and optional description for each role. Choose from the server-emoji selector or paste <:name:id> for static emojis or <a:name:id> for animated emojis. Core checks emoji access and role restrictions before saving and publishing. The automatic embed guide explains which choice gives which role.
3. Starter, verified, and privileged roles cannot be offered. Each role can belong to one menu. Members’ unrelated roles are preserved.
4. Optionally require the verified-member role. Enable rules acceptance first if you use this option.
5. Save and publish each panel. Updates edit an existing panel in the same channel. Changed or paused panels cannot grant roles until their current settings are published.
6. Buttons toggle roles; a limit of one replaces the previous choice. Dropdowns replace only the choices in that panel; clearing removes them. Reactions grant a role when added and remove it when removed. Reaction panels allow multiple roles without exclusive limits. Core needs Add Reactions and Read Message History in the selected channel.

Configure goodbye messages

1. Choose a separate channel and departure message in Goodbye messages. Choose simple text, a branded embed, or a graphical card with a custom title, colour and footer.
2. Use the same four welcome placeholders. A departing member is represented by their name, without a notification.
3. For cards, upload a PNG, JPEG or WebP background up to 5 MB. Recommended resolution: 1000 × 340 px. Core needs Embed Links for embeds and Attach Files for cards.
4. Save before using Send test. The test uses your account as the sample member and never notifies anyone.
5. Enable and save. Future human departures are handled while goodbye messages are enabled and member events are available.

Collect ideas and make decisions

1. Choose a suggestions channel and a per-member submission cooldown from 1 to 1,440 minutes. Enable and save suggestions.
2. Publish the suggestions panel. Members submit an idea of 10–1,000 characters through its button and form.
3. Exact duplicate text is detected after case and whitespace normalization. Members can change or remove their vote by clicking the support or against buttons.
4. The dashboard lists the latest 30 suggestions. Mark an idea Reviewing, Planned, Completed, or Declined and optionally add a public staff response.
5. Completed and declined ideas close voting. A saved suggestion whose Discord delivery was uncertain is identified in the dashboard; check the channel before attempting further publication.

Create events and configure automatic reminders

Discord holds the event itself. Core reads its schedule and provides an optional public directory plus automatic reminders.

1. In Discord, open the server Events menu and create a scheduled event with its name, description, time and voice channel or external location. Use Discord’s Scheduled Events guide if you need help. Core has no separate event creation form.
2. Open Community events inside that server’s Core dashboard. Select the channel where reminders and the directory should appear. Core needs View Channel, Send Messages and Embed Links. Choose a channel your audience can read.
3. Select a lead time: 5, 15, 30 or 60 minutes, or one day before the start. Optionally select an ordinary, mentionable event-notification role. Offer it through Self-service roles so members can opt in. Without this role, reminders post without a ping.
4. Enable event reminders and save changes. This starts reminders independently of the optional directory. Unsaved settings do not change the live schedule.
5. Review upcoming and active event cards for descriptions, start/end times, location and Interested counts when Discord provides them. Browser times use your local timezone; Discord timestamps adapt to each member. Reload after changing events in Discord.

Discord’s official Scheduled Events guide

Publish the optional event directory

1. Save and enable events before publishing. Select Publish event directory to post one message linking the next ten scheduled events visible to everyone in the server. Publishing does not ping members.
2. The directory is a snapshot. Adding, cancelling or rescheduling an event in Discord does not automatically edit this message. Reload the dashboard, then select Update event directory.
3. Updates edit the existing message when the destination is unchanged. A deleted message is recreated. View directory opens the actual Discord message.
4. Private events visible to authorized managers can appear in the dashboard, but are excluded from public directories and reminders. Active events can appear in the dashboard but are excluded from the upcoming directory.

Understand timing, notifications and interruptions

1. Core checks approximately once per minute. For an 8:00 PM event with a 15-minute lead, it can send on the first check after 7:45 PM while the event remains scheduled and has not started.
2. Discord’s Interested response is separate from Core’s opt-in role. Discord can notify Interested members when the event starts; Core’s earlier reminder pings only the selected role. It never pings everyone.
3. Core checks the current event before sending. Cancelled, active and past events are skipped. Rescheduling can create a new reminder for the changed start time.
4. If Core reconnects during the reminder window, it can send before the event starts. Missed past events are not replayed, and uncertain sends are not automatically retried because delivery may already have happened.
5. Turn off Enable event reminders and save to stop future reminders. Existing directory messages remain; other Core features continue. Check Recent activity and live Status if a delivery needs investigation.

Publish rules acceptance

1. Choose a verification channel newcomers can see. Write the rules or point to your rules channel.
2. Choose a safe verified-member role below Core’s role. Do not also grant it automatically on joining. Optionally choose a starter role to remove after acceptance.
3. Enable rules acceptance, save, then select Publish panel to Discord. This sends the real Accept rules & verify button.
4. Republish after changing the panel’s channel, message, or roles. Outdated panels cannot grant access.
5. Configure member-only channel access in Discord using the verified role. Core does not change channel permissions; rules acceptance is not identity verification or a CAPTCHA.

Review, reload, or pause

1. Recent activity helps explain onboarding outcomes. Reload refreshes access information and asks before discarding unsaved changes.
2. Turn an individual feature off and save to stop its future actions. Other enabled features continue. Posted messages and existing member roles remain.
3. Settings apply only to the selected server. Review the server name before every save.

Commands & controls

Use these controls for the current release inside the relevant Discord server. Discord’s command picker supplies required options; app-specific permissions still apply.

What this app needs and keeps

Discord access

Core needs access to the chosen channels and Manage Roles for onboarding roles. Your Discord permissions and Core’s role position are checked before changes; the public invite does not request Administrator.

Stored information

Core stores server-specific settings, panel references, recent activity, submitted suggestions, votes, staff decisions, and event reminder delivery claims. The rules panel records the configured workflow; accepting rules is not a CAPTCHA, identity verification, or proof that someone is safe.

Troubleshooting

Still stuck? Check Service Status, then contact private support with the app, server ID, and the error. Never send a password, bot token, or backup code.