Guild-scoped privacy
Keep private rosters and financial details behind authorization while exposing only the alliance information a role is allowed to see.
Alliance command
Coordinate multi-guild alliances across servers and factions
An alliance is more than a larger roster. It needs clear membership boundaries, shared rules, and visibility that does not expose one guild’s private data to another. ForgeKeep gives authorized leaders a coordinated view of Alliances and Faction operations while guild records remain scoped to the access granted.
Dashboard field guide
See alliance management 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.
Shared operations
Coordinate events, faction inventory, item requests, and shared rules without flattening every guild into one account.
Clear ownership
Assign alliance and faction responsibilities so decisions remain attributable across a larger command structure.
Operational flow
How the workflow fits together
- 01
Establish the network
Create the alliance, connect participating factions or guilds, and define leadership access.
- 02
Coordinate activity
Use shared alliance and faction views for events, inventory requests, and cross-guild work.
- 03
Audit boundaries
Review alliance actions while preserving each guild’s permissions and private records.
Related guild operations
Start with your current operation
Bring alliance management 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.