Documentation
Back to tutorials

Data

Data Inventory Use Cases

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

Who uses it

Owners, managers, data-minded staff

Where it lives

Dashboard > Data Inventory

Goal

Staff can identify useful data, export it safely, and spot missing capture points.

Before You Start

  • Analytics or data inventory permission.
  • A guild with packs, verifications, tickets, notifications, or events.

Steps

1

Read the inventory by object family

Use tabs or families to inspect content, verification sessions, members, support tickets, notifications, RaidHelper reports, marketplace data, and operations events.

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

Use family exports when a focused CSV or JSON is enough. Full inventory exports are better for audits, handoffs, or support-assisted reviews.

4

Turn gaps into clear actions

If a field is missing, first check whether the page offers a staff action. If it does not, note which workflow is blocked and share that context with GearCheck support.

Launch Checklist

  • The family count matches what staff expect.
  • Export buttons produce clean files.
  • Known gaps are understood before relying 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 Data Inventory as analytics instead of a map of owned data.

Related