How does Invites work?
Follow member arrival sources, manage links, and define qualified joins.
What should I know about start tracking?
Open Invites in your server dashboard and choose Set up tracking. Yuna needs Manage Server to read invite-use counts. Tracking begins with a fresh baseline; it cannot reconstruct members who joined before it was enabled. Overview shows observed joins, attributed sources, exclusions, and qualified members. Links lists Discord invite links with optional campaign labels. Members contains private arrival history.
What should I know about the counts?
Discord does not tell bots which invite a member used. Yuna batches arrivals and compares invite-use counts. A single matching counter change can identify a source; simultaneous changes, disappearing links, and connection gaps remain unknown or ambiguous. Vanity joins have no link owner. The link owner created the invite and may not be the person who shared it. Discord uses include activity from before tracking. Departures while Yuna is offline may be missing; remaining-member counts use observed departures.
What should I know about define a qualified join?
In Settings, choose a minimum account age, time in the server, optional Discord membership screening, and excluded roles. Rules apply to future arrivals. Bots, blocked arrivals, and returning members do not qualify. A qualified member must still have no observed departure. Staff can add a reason to exclude an arrival, or clear that staff exclusion without overriding automatic rules. Raw joins and their source remain visible.
How do I manage links?
Create a link for a text channel with a configurable lifetime and maximum uses. Zero means no expiry or unlimited uses. Yuna owns links it creates; labels distinguish campaigns. Revoking stops new use without deleting arrival history. If Discord cannot confirm a creation or revocation, Yuna does not repeat the uncertain action. Check the link list and Discord before creating another.
What should I know about access and retention?
Invite statistics are staff-only by default. Settings can allow members to see their own statistics or everyone and the leaderboard. Use /invites stats and /invites leaderboard; slash replies are private. Private prefix results are sent by DM. Staff Access separates aggregate statistics, private links and member records, and record management. Only Yuna owners configure tracking or create dashboard links. History is retained for 30 to 365 days; changes apply to future arrivals. Returning-member detection lasts while the minimal arrival marker is retained. Optional channel notifications support a custom message and role or @here notifications. Automatic invite rewards are not included. Server Activity remains a separate, optional source of participation insights.