FAQ

Modfolio is a professional network for community moderators. You build a profile with experiences, skills, and references so communities can find and trust staff who have real moderation history.

For experiences you proved through Discord (self-proven or server-verified), Modfolio periodically checks whether you still hold a staff role. It uses two signals when available:

• Your Discord login and server list (OAuth), refreshed on sign-in, manual refresh, and a weekly background sync.
• The Modfolio bot's live staff roster on communities where the bot is installed and staff roles are configured.

When a check succeeds and shows a promotion, demotion, or leave, Modfolio updates that experience automatically. Silence alone (for example, not opening the app for a while) does not invent a leave date.

Unconfirmed means Modfolio could not verify that you still hold the role. The experience stays on your profile with its history, but it is no longer treated as trusted current staff (including in recruit filters).

This usually happens when Discord reconnect fails and the bot cannot vouch for that server either. Reconnect Discord (or restore bot access on that community) so Modfolio can confirm again. We do not invent an end date just because a sync failed.

If the Modfolio bot is still on that server and still sees you on a mapped staff role, your current experience can stay confirmed. You will still be asked to reconnect Discord so Modfolio can refresh your server list for claims and new proofs. If the bot cannot confirm you either, the experience becomes unconfirmed until something can verify it again.

Modfolio falls back to your Discord server list. Promotions, demotions, and leaves are driven from that OAuth data while the bot is unavailable. If both Discord login and the bot fail for that community, current experiences there become unconfirmed.

When Modfolio successfully sees that you left or lost staff status (through the bot roster, or through Discord login when the bot cannot answer), it ends the current experience on the day of that evidence, or updates the role level if you still hold a lower staff role. After an experience ends, Modfolio does not silently reopen it if you rejoin later. You add a new stint or request career verification for past tenure.

No. Experiences marked as claimed are assertions, not Discord proofs. Modfolio never auto-promotes, demotes, or ends them from OAuth or bot signals. Changes there stay manual or go through attestation flows.

Modfolio refreshes it when you sign in with Discord, when you use Refresh on suggested actions, and about weekly in the background if your list is getting old.

• After about 14 days without a successful refresh, you may see an in-app warning to refresh.
• After about 30 days (or if the list is empty), Modfolio blocks new self-proven adds and some claim proofs until you refresh or reconnect.

A temporary Discord outage does not mark experiences unconfirmed. Modfolio retries later without clearing your connection.

Sign in with Discord on the login page. Modfolio uses Discord as the primary identity so your server membership and badges can power verification. After the first sign-in you go through a short onboarding flow for your profile and linked accounts.

Moderation careers live on Discord. Connecting Discord lets Modfolio see which servers you are in (with your permission), prove current staff roles where possible, and keep experiences honest over time. You can still fill in claimed history and references without every server installing the bot.

Yes. From settings or onboarding you can connect additional accounts that show on your profile. Discord stays primary for login and verification. You can unlink secondary connections later without deleting your Modfolio account.

Open Security settings to enroll TOTP or a passkey. Staff accounts may be required to complete step-up verification before sensitive admin actions. Treat Discord login as the front door: keep Discord 2FA on as well.

Your display name, handle, bio, avatar and banner, career timeline, skills, languages, availability, connected accounts, and references you choose to show. Privacy settings control what logged-out visitors see. Suspended or banned accounts stay visible with a status notice rather than vanishing.

Common paths:

• Self-proven: current staff status inferred from your Discord permissions or owner status on a server you are in.
• Server-verified: confirmed against designated staff roles when the community runs the Modfolio bot.
• Claimed: history you assert yourself, useful for past tenure that Discord cannot prove today.

Communities with mapped staff roles may require you to pick one of those roles instead of a free-text title.

You can request references from people who know your moderation work. They respond in Modfolio; approved references can appear on your profile. References are not Discord role proofs. They are peer attestations that recruiters can read alongside your timeline.

On first Discord sign-in, Modfolio can copy your Discord avatar and banner (if you have a banner image) into Modfolio storage. You can replace either anytime from your profile. Changing Discord later does not overwrite a Modfolio image you already set.

Start from Claim a server. Owner or admin-style Discord permissions are usually enough for an automated claim. Installing the Modfolio bot finishes setup so staff roles, roster checks, and recruiting tools can work.

The bot syncs Discord role names and colors, lets you map staff roles to position titles, and can confirm who currently holds those roles. On large servers it may check a person's roles on demand instead of walking the entire member list. It does not moderate your Discord chat or replace your staff tools.

Mapping tells Modfolio which Discord roles count as moderator, manager, or admin for verification and recruiting filters. Without mapped roles, people can still claim experience, but server-verified current staff proofs need those designations.

Community owners can invite teammates from the server's team settings. Invites can target a Modfolio profile or a Discord user. Permissions control who can manage roles, listings, billing, and other settings.

Browse Roles or Discover. Listings can filter on verified experience, skills, languages, and more. Sign in so applications and profile matches work correctly.

Open a listing and submit an application from your Modfolio profile. Communities review applicants in their recruiting pipeline. You can track status under Applications.

After you claim a server and finish basic setup, open that community's recruit tools to create a listing, set filters, and review applicants. Stronger verification signals (bot installed, staff roles mapped) help applicants prove they are a fit.

You can create a profile, prove experiences, and browse roles on the free plan. Paid plans unlock premium profile and community team features. See Pricing for current options. Billing for communities is managed from the community billing page once you are on the team.

Account identity from Discord (and any accounts you link), profile content you enter, experience and verification records, community membership and role mappings for servers you manage, application activity, and operational logs needed to run the product. Details live in the Privacy Policy.

Yes. Use Data settings or the data request flow for export and erasure requests under applicable privacy law. Some records may be retained where we must (for example abuse prevention or legal holds).

Open Email preferences. Transactional mail (security, essential product notices) still sends. Marketing and optional activity categories can be turned off, and many messages include a one-click unsubscribe link.

Use the Support form to open a ticket. You can follow up in the ticket thread after you submit. For product rules see Terms of Service.