Join log: who joined, and who invited them
Log every member who joins or leaves your Discord server, with their account age and which invite, and whose, they used.
Pick a channel in the 📥 Join log menu of /config (a private staff channel works best, and it can be your log channel). Stingsby then posts every member who joins or leaves. For a join:
| Field | What it shows |
|---|---|
| User | Mention, username and ID, with their avatar |
| Joined at | The date and time they joined, to the second |
| Member | Their member number, e.g. #1,234 |
| Account created · Account age | When the account was made and how old it was when it joined. Accounts under a week old are flagged ⚠️ and the post turns orange |
| 📥 Invited by | Who created the invite they used, the invite code, its channel and how many times it has been used |
How stingsby knows who invited them
Discord doesn't say which invite someone used. Stingsby keeps a count of how often each invite has been used, and when a member joins it checks which count went up:
- One invite went up: that invite and the person who created it.
- The vanity URL went up: your server's vanity URL.
- A single-use invite disappeared: that invite, because Discord deletes it as it's used.
- Several went up at once (people joining in the same second): all of them, listed as candidates.
- Nothing changed: "couldn't tell", for example Server Discovery, or an invite created and used while stingsby was offline. Bots are shown as added by an admin, because they don't use invites.
Leaves
Leaves go to the same channel, as 📤 Member left: when they left, how many members are left, when they joined and how long they stayed (under a day is flagged ⚠️), their account age, and how they joined. When stingsby itself removed them (a trap ban or softban), the post is red and says so.
Leaving never lowers an invite's count. Discord's use count includes everyone who joined through an invite, even people who left later, and stingsby only looks at counts that go up.
Joins and leaves are also saved to the event log: /honeypot logs kind:Joins and leaves lists them, and user: shows one person's joins and leaves. Ban reports show how the caught account joined, so you can spot one invite bringing in several spam accounts.
Reading invites needs the Manage Server permission, which stingsby isn't given when it's added. Give it to the stingsby role (Server Settings → Roles). Without it every join is still posted, just without who invited them, and /config and /security scan warn you.