Working Inside an Alliance

Alliance work brings together the roster, manual input, imports, event results, reports, and selected analytics. Open My Alliance or the assigned alliance management view when available.

Manager workflow

Confirm the alliance, review current members, resolve duplicates or link requests, enter or import event information, and verify results before using them for rewards or reports. Co-leaders see only the actions granted to their assignment.

Do not use an alliance screen to infer access to another alliance in the same kingdom. Ask a kingdom manager when a cross-alliance correction is needed.

Alliance manager workspace landmarks

Check the selected alliance before changing roster or event records.

• Alliance tag and name in the active context.
• Player roster with status, attributes, participation, and result indicators.
• Event instances, manual entry, screenshot imports, and review queues for that alliance.
• Alliance Analytics, rewards, and subscription state with role-dependent actions.

Related guides

• manage players
• review and history

Practical depth

An alliance operating rhythm

Maintain roster identity before collecting evidence. Review warnings during input, inspect coverage after the event, correct source rows where necessary, and publish rewards or reports only from an agreed date window and rule set.

Purpose, example, and limits

Alliance work keeps roster, entry, import review, correction, Analytics, and rewards within one assigned community. Example: A co-leader applies eligible rows but cannot resolve one locked conflict. The accepted rows remain staged and the locked row is handed to the alliance leader with batch, event, date, and message. The leader resolves and applies, then both verify Alliance Analytics. A role cannot cross into another alliance or turn shared Analytics into edit access. Troubleshoot at the owning player, event, or batch rather than duplicating it.

Limitations include the alliance member cap, event locks, feature and plan state, source retention, and assignment-specific actions. The output remains scoped history and summaries; offline agreements or unrecorded activity are not inferred.