Back to Guides Hub

Best practice setup

CLNR Bulk Upload Guide

Understand why CLNR does not auto-import your full member roster after installation, how to seed known members quickly with /bulk_user_upload, and where /checkin fits when members can acknowledge a post with reactions.

Invite CLNR Open command reference

Why CLNR does not auto-import every member

CLNR is built around a privacy-first model and does not rely on privileged intents for core operation. That means it does not automatically pull a complete member roster at install time.

Normal inactivity tracking still works without any bulk import. As members interact and admins use regular commands, CLNR learns and tracks them over time.

When bulk upload helps: large or structured communities that already maintain a known roster and want faster day-one coverage. When you do not have a clean roster, /checkin can ask members to react to a server reminder so coverage grows through normal reaction activity.

What /bulk_user_upload does

  • You can provide either comma-separated IDs (ids) or a CSV attachment (file).
  • CLNR checks those IDs against your current server.
  • Valid members are seeded for inactivity tracking faster.
  • Existing known members are skipped as already known.
  • Every run starts with a preflight summary before processing begins.
  • The command keeps CLNR's privacy model intact and does not require message content access.

Preflight and Free-tier automation status

Before CLNR imports anything, admins see current tracked members, valid IDs parsed, estimated tracked members after upload, and the relevant tier limit.

Free tier: Bulk Upload is available as a coverage helper. If a Free server goes above 200 tracked members, CLNR pauses all automations for that server until Pro or Scale is active. Reports and manual review may still be available.

Where /checkin fits

Bulk upload is best when staff already have member IDs. If coverage is low because many members have not interacted yet, admins can use /checkin to publish a structured reminder that members acknowledge with reactions.

  • CLNR checks that reactions count as activity before publishing.
  • The target channel must be tracked and CLNR must have the needed channel permissions.
  • Check-ins use the normal reaction activity flow instead of creating a separate attendance system.

How to get user IDs

CLNR does not generate a full member ID export by itself. Use this command when you already have a member roster.

Some admins use third-party tools to export members and then copy IDs into CLNR. Two examples tested by our team:

MemberList

/server filetype:csv

ServerStats

/members filter:members only file:csv file

Third-party note: these tools are not operated by CLNR. We do not control their uptime, output format, permissions, or privacy practices.

Recommended upload workflow

  1. Export member IDs from your trusted roster source.
  2. Preferred path: upload the CSV directly via /bulk_user_upload file:<members.csv>.
  3. Alternative path: use ids with comma-separated IDs (up to 250 unique IDs per run).
  4. Review the preflight summary and continue only when the tracked-member impact is clear.
  5. Watch progress updates and read the final summary.
  6. CSV mode handles full files in internal batches; manual ids mode may require repeated runs.

Understanding the result summary

added: members successfully registered for tracking.
known: members already known to CLNR.
not found: ID not found or user not in your server.
invalid: entry is not a valid user ID.
error: CLNR could not fetch that ID at this moment.

Limits and plan notes

  • /bulk_user_upload is available on Free, Pro, and Scale.
  • On Free, CLNR can manage up to 200 tracked members. Above that limit, all automations pause until Pro or Scale is active.
  • Manual ids mode keeps the existing 250 unique IDs per command limit.
  • CSV file mode does not apply the 250-ID per-command cap and processes full files in internal batches.
  • Bulk upload is optional. Normal inactivity tracking continues to work without it.

Next steps

If your current coverage is below target, run /coverage first, then seed with /bulk_user_upload when you have IDs, or use /checkin when you want members to acknowledge a reminder with reactions.

Open /coverage docs Open /bulk_user_upload docs Open /checkin docs