Source context
Record where an item came from, including the related boss or guild activity when available.
Vault control
Track guild inventory from boss drop to final distribution
A guild bank spreadsheet becomes unreliable as soon as drops, requests, auctions, and distributions happen in different channels. ForgeKeep’s Guild Storage keeps the vault, auctions, bids, settlements, and history in one operational flow with source context and status changes that authorized members can review.
Dashboard field guide
See guild inventory in motion.
A sample view of the ForgeKeep dashboard, with the exact records and handoffs this feature is designed to keep together.
Why it matters
Replace disconnected updates with a reviewable workflow.
Current status
See whether an item is stored, requested, listed, bid on, settled, or distributed.
Permission-aware access
Keep operational inventory behind guild authorization instead of publishing item or member data to search engines.
Operational flow
How the workflow fits together
- 01
Log the drop
Add the item with its source, quantity, relevant metadata, and storage destination.
- 02
Route the item
Process requests, auction listings, bids, settlements, or distribution according to guild rules.
- 03
Reconcile the record
Review history and settlement outcomes so the vault count stays explainable.
Related guild operations
Start with your current operation
Bring guild inventory into the same guild record.
Create a workspace, invite the right officers, and migrate one workflow at a time. Private guild data stays behind application authorization.