Understand and set up Modara.

1. Sign in with Discord and select your server. Your Discord account needs Manage Server or Administrator permission.
2. Add the bot from the server selection and check its permissions in the channels you want to use.
3. Open Community in the dashboard, configure the modules you need and save your changes. Existing onboarding and AI options are also available under Settings.

Configuration always applies to the selected server. Changing its community modules requires owner or administrator access in the dashboard.

Yes. Welcome messages, social alerts, reaction roles, XP, polls, giveaways and economy each have their own switch under Community. Choose the state you want and save. The developer API has a separate switch in the developer section.

Disabling stops use of that module. Settings, earned XP, coins and existing entries are retained. Previously assigned Discord roles and published messages remain; disabled role buttons and reactions do not change roles.

Poll and giveaway deadlines keep running. Votes and entries are blocked while paused. A deadline reached during the pause is processed after you enable the module again; the duration is not extended.

For welcomes, alerts, polls and giveaways, Modara must be able to view the destination channel and send messages. Embedded messages also need Embed Links. Role features require Manage Roles, and Modara's role must be above every role it should assign or remove.

Emoji reaction roles also need Add Reactions and Read Message History. Moderation actions need their corresponding permissions, such as Moderate Members for timeouts. Channel overrides and the role hierarchy still apply.

The bot operator must enable member access for join events. Content-based features such as Catchup and AutoMod also need message-content access. A module switch does not replace these Discord permissions.

Modara automatically welcomes new members in your chosen text channel. Open Community → Welcome messages, select a channel and write your template. Check the preview with example data and save the settings. Then enable the module and save its status.

These placeholders are replaced when a member joins:

{member}

Mention of the new member

{username}

Username

{server}

Server name

{memberCount}

Current member count

Example: Welcome {member} to {server}! Check #rules first. We now have {memberCount} members.

The welcome switch controls the greeting. Set an automatic join role separately under onboarding in Settings. No new greetings are sent while the welcome module is off.

Modara periodically checks connected sources and posts new Twitch livestreams, YouTube videos or Bluesky posts in your Discord channel. Notifications can therefore arrive a little later than the original.

1. Enable social notifications under Community.
2. Choose Twitch, YouTube or Bluesky, enter the source requested by the form and select the destination channel.
3. Save the source. You can pause individual sources or the entire module.

Twitch and YouTube require a provider connection configured by the Modara operator. Their alerts cannot be fetched without it. The three listed providers are supported.

Reaction roles let members choose an available role themselves. Enable the role module under Community and create a role panel: select the destination channel, title and role, then choose a button or emoji reaction and publish.

Clicking the button adds the role; clicking again removes it. For emoji panels, adding the reaction assigns the role and removing it removes the role. Use a standard Unicode emoji, such as 🎮.

The target role must be below Modara's role and manageable by the bot. Administrative permissions do not belong in self-service roles. Turning the module off preserves assigned roles and prevents the panel from assigning or removing more roles.

Enable leveling under Community. New member messages can earn XP. By default, an eligible message earns 10 XP, at most once every 60 seconds per member. Bot messages do not count.

The dashboard lets you set 1–100 XP per message and a cooldown of 15–3,600 seconds. Also select the channel for level-up messages. Members use /rank to view their progress and /leaderboard for the server ranking.

The level is the square root of XP ÷ 100, rounded down: level 1 starts at 100 XP, level 2 at 400 XP and level 3 at 900 XP. XP and levels are tracked per server. Turning the module off pauses rewards and level commands; progress is retained.

1. Enable polls under Community and select the Discord destination channel.
2. Enter a question, two to five answer options and a duration.
3. Publish the poll. Members vote using the buttons in its Discord message.

Each member has one vote per poll; a submitted vote cannot be changed. No more votes are accepted after the deadline, and the result is finalized. Votes are retained across bot restarts.

Turning polls off blocks new votes. Deadlines keep running; overdue polls are finalized after you turn the module back on.

Enable giveaways under Community, select a channel, describe the prize and set the duration. Starting publishes a message with an entry button. Each member can enter once; repeated clicks do not increase their chance of winning.

After the deadline, Modara randomly selects one winner from the saved entries. The selection is stored. A restart does not simply redraw a winner already selected. If there are no entries, there is no winner.

Your team delivers the announced prize. Turning the module off pauses processing and blocks new entries; the deadline stays in place. Cancel ends an individual giveaway without a draw.

Economy gives your server a virtual coin currency. Enable it under Community. Balances belong to a member on that specific Discord server.

• /balance — shows your balance.
• /daily — claims 100 coins, once every 24 hours.
• /pay member amount — transfers a positive whole number of coins to another member of the same server, if you have sufficient funds.

Coins are game points with no real-money value and cannot be cashed out. They are separate from XP. Turning economy off blocks these commands; existing balances are retained.

Enable AI under Settings if your plan includes it. Ask community questions in Copilot; Insights help interpret existing activity data. AI needs a configured provider connection and available AI allowance. Check recommendations against your server.

In AI Server Setup, describe your intended community. Modara proposes channels and roles for you to review and confirm before creation. This section requires Business and server-owner access. A proposal alone does not change your server.

For a weekly report, enable it in Settings and choose its destination channel. Configure automatic moderation rules separately in the moderation section.

Enable AI and allow Catchup channels under Settings. In an allowed Discord channel, use /catchup hours:6, for example. You can request 1–24 hours; omitting hours requests six. Catchup is included in Pro and Business and needs AI allowance.

You and the bot need access to the channel and its history. Modara reads accessible recent messages to produce the summary. The result states its actual coverage and marks a partial summary when reading limits were reached. The summary is stored, not a complete chat archive.

Your team handles individual cases with commands such as /warn, /timeout, /kick and /ban. Supply a reason and use actions for which both your account and Modara have the required Discord permissions. Find case history in the dashboard; members can submit an appeal with /appeal.

AutoMod checks new messages against enabled rules, such as spam, invites, links and blocked words. Configure rules, exceptions, thresholds and actions in moderation settings. Use the simulator to check your rules. Enabled AutoMod rules can actually delete, warn, time out or ban.

AutoMod requires Pro or Business; AI context review is a separate Business option. Turning AutoMod off stops new automatic checks and does not undo existing sanctions.

Overview and Analytics show tracked messages, active members, joins, leaves and the most active channels. Select an available period in the dashboard. Numbers come from recorded events; a newly connected server does not yet have a complete history.

The Community Health Score combines signals including activity, retention, onboarding, moderation and support responses. If required signals are missing, Modara does not invent a score. It helps with interpretation and does not replace your team's judgment.

You can retrieve aggregated statistics for your own website using the developer API. Read the API guide

Members open a support ticket in Discord with /ticket and a subject. Modara creates a private ticket channel; the bot needs the required channel permissions. Your team handles the request in the Support section.

There you can reply, assign staff, hand over internally and close tickets. Configure response deadlines, overdue alerts and optional ratings in Support. An authorized staff member reviews an AI reply draft before sending it.

Open Command Center, search for a command or filter by category and status. Expand an entry, adjust its available settings and save. You can create custom text responses with names, aliases, role requirements and cooldowns.

Custom text commands use the configured prefix. Discord slash commands start with /. Module-specific commands, such as XP or coin commands, also depend on the corresponding module switch. /help opens the bot's command help.

In Business, create if-then workflows under Automations, such as a welcome message on join or a role assignment on a matching trigger. Supported triggers are member join, member leave and a message containing text; actions are sending messages and assigning roles. A member who has left cannot be assigned a role. Each workflow can be paused separately.

In Business, scheduled messages are sent at a chosen time and can repeat. Follow the form's UTC time zone and a minimum of 15 minutes between repeats. Temporary voice rooms are created through a configured creation lobby; this feature is available from Pro. Event logs record selected event metadata.

1. Open the selected server's developer section, enable the API and create a key with permission to read statistics.
2. Store the key only on your own server, for example as an environment variable. Your backend calls the Modara API and passes only the required statistics to your website.
3. Use the documented endpoints and error codes. Statistics requests support days from 1 to 90. The available history depends on when Modara started tracking events.

A key is bound to exactly one server and grants access to statistics, not bot control. Never put it in browser JavaScript, public repositories or a URL. You can revoke individual keys or turn all API access off.

1. Is the correct server selected, was the change saved, and is Modara online in Discord?
2. Does the plan include the module? For social alerts, is the individual source enabled? For commands, is the individual command enabled?
3. Can the bot view the destination channel and send messages there? For roles, are the permissions and role hierarchy correct?
4. Is a cooldown active, has the poll ended, or is an AI or social connection missing? Check the specific error in the dashboard or Discord.

If delivery status is unclear, check the destination channel before publishing the same message or panel again.

Modara stores server settings, statistical values and data from features in use, such as XP, balances, poll votes and giveaway entries. Tickets contain messages saved for support. Analytics and event logs are not a complete Discord chat archive.

Switching a module off is a pause, not data deletion. Manage personal data under Account → Privacy; stored server data is deleted separately in server settings. Read the effects there before confirming.