Skip to content
Tutorials

Stored Data Use Cases

Understand what data your guild produces, owns, exports, and can use for staff operations.

Data and Status
Who uses it
Owners, managers, data-minded staff
Where it lives
Dashboard > Stored Data
Goal
Staff can see what GearCheck stores, where each kind is managed, and how to download a copy.
On This Page5 sections

Before You Start

  • Analytics or stored data permission.
  • A guild with packs, gear checks, tickets, notifications, or events.

Steps

  1. Read the stored data by object family

    Use the kinds filter to read one kind at a time: settings and staff, packs and builds, gear checks, members and characters, tickets and reviews, Raid-Helper readiness, and the Marketplace. A count that comes from the audit log says so, and reads Didn't load when the log does not answer.

  2. Look for practical uses

    Each family should answer a staff question: who is ready, what build fails, what tickets repeat, what events fired, what exports exist, and what data the guild can manipulate.

  3. Export only what you need

    Export one kind at a time. Each file uses one of the month's exports on a metered plan.

  4. Fix what is not set

    A row that reads Not set says where to set it: most link to the page, and the ticket row names the Discord commands. The line under each kind opens the pages that manage it.

Check It Worked

  • The family count matches what staff expect.
  • Export buttons produce clean files.
  • Every Not set row is understood before you rely on the data.
  • Private IDs and sensitive evidence are handled intentionally.

Common Pitfalls

  • Exporting raw data without a reason.
  • Assuming every object has display-ready names when some still store IDs.
  • Treating Stored Data as analytics instead of a map of owned data.