CLNR Bulk Upload Guide
Seed known Discord members quickly with /bulk_user_upload. Review roster impact, optional restore/swap roles, plan capacity limits, and import results before execution, all without requesting privileged member intents.
Example values, not live data or default settings.
4-Step Bulk Upload Workflow
Seed known current members safely while keeping total control over server capacity and role assignments.
Prepare Known IDs or CSV
Gather member IDs from your existing roster or export utilities. Prepare an attached CSV file (up to 2 MB) or comma-separated string (up to 250 unique IDs).
Review Preflight & Roles
Execute /bulk_user_upload. The interactive preflight output checks server membership, skips duplicate tracked users, and calculates capacity impact.
Confirm or Stop Import
Check capacity limits and optional role assignment parameters (apply_default_role). Click Continue Upload to process, or Cancel before starting. During processing, use Stop Upload to stop further work; members already seeded remain tracked.
Inspect Result Summary
Review the final summary screen. View total processed, newly Seeded, Known, Not Found, Invalid, and Failed counts, along with applied roles.
Why CLNR does not auto-import every member
CLNR operates under a strict privacy-first model and intentionally runs without requesting privileged member intents or message content access permissions.
As a result, CLNR does not automatically pull or store your server's entire member roster upon installation. Under standard operation, tracking coverage grows organically as members participate in activity events or are explicitly seeded by authorized staff.
Seeding Without Privileged Intents
Existing members are not scored retroactively from their join date. Executing /bulk_user_upload seeds current human members so inactivity tracking and Activity Health Scores can start from a more complete tracked roster.
- Seeding adds members to tracking; it does not reconstruct past activity or guarantee complete reporting context.
- Use /coverage at any time to verify current tracked count and estimated server coverage.
- Read the complete How It Works guide for details on CLNR's zero-message-reading guarantee.
Import behavior & verification rules
Run Bulk Upload in your server with active CLNR admin access. Input parsing filters invalid strings; processing verifies current membership, skips bot accounts, and enforces safety boundaries.
- Flexible Inputs: Provide user IDs via attached CSV file (file, max 2 MB) or comma-separated strings (ids, max 250 unique IDs). Use exactly one input mode per run. The 250-ID command limit does not apply to CSV files; upload safety limits still apply.
- Server Verification: CLNR validates IDs against current server membership and automatically excludes bot accounts. An ID in a CSV file is not proof of current membership.
- Automatic Deduplication: Members already tracked by CLNR are skipped automatically.
- Role Restorations & Swaps: Optionally applies configured restore/swap roles to newly seeded members. If roles are configured and apply_default_role is omitted, preflight asks whether to apply them. If no roles are configured, that question is skipped.
Effective capacity & Free-tier limits
Before an upload starts, preflight shows your current tracked member count, valid parsed IDs, projected post-upload total, and plan limits.
Plan Capacity Rules
- Effective tracked capacity depends on your server's plan and may include an earned voting buffer. Always verify current server capacity rather than treating screenshot figures as hardcoded defaults.
- On over-limit Free servers, automated communication and actions pause; unmanaged background work may also be reduced. Long-dormant servers may have nonessential activity data pruned.
- Stored settings and supported admin commands remain available; manual checks still follow their plan requirements. Compare tier limits on our Pricing page.
Where /checkin and polls fit
If your team does not possess an exported CSV or roster list, bulk upload is not required. Administrators can use policy reminders or check-ins to invite participation organically.
- Policy Reminders: Launched via /checkin wizard, using reaction acknowledgement. Reaction tracking can add members to CLNR tracking. Acknowledging a policy is not proof of wider engagement.
- Community Restart Check-Ins: Use anonymous single-choice buttons. Individual choices are deleted immediately after aggregation; button clicks count toward activity only when Commands/Components tracking is enabled.
- Scheduled Community Check-Ins: Configured through /polls_wizard for selected topics in a dedicated channel. They use anonymous single-choice buttons and aggregate results; individual choices are deleted after aggregation. Explore Community Check-Ins for details.
- Polls & Quizzes: Also configured through /polls_wizard, these use reaction voting. Explore Polls & Quizzes for details.
Obtaining user IDs for upload
CLNR does not export a complete server member list. Use an existing roster or a server management bot to obtain user IDs.
Roster Export Examples
MemberList Export
/server filetype:csv
ServerStats Export
/members filter:members only file:csv file
Bulk Upload & Roster Commands
Server owners, Discord Administrators, and members of the configured CLNR admin role can use these commands to inspect coverage, seed rosters, and configure check-ins.
Seeds known current members into CLNR tracking via an attached CSV file (file, max 2 MB) or comma-separated string (ids, max 250 unique IDs). Executes interactive preflight check before processing.
Reports managed member count and estimated server coverage. A coverage percentage is shown when a server-total estimate is available. Use after bulk upload to verify roster state.
Launches the setup wizard for policy acknowledgement reminders or anonymous Community Restart check-ins. Policy reminders use reactions; Community Restart uses anonymous buttons, which count toward activity only when Commands/Components tracking is enabled.
Configures reaction-based Fun Polls and Quizzes and scheduled Community Check-Ins with anonymous single-choice buttons. Individual check-in choices are deleted after aggregation.