Theme
Alliance Leader or Co-leader
Maintain the assigned alliance roster, review contributions, enter or import event information, verify results, and use scoped reports. A co-leader sees only actions included in the assignment.
Recommended sequence
- Sign in when the workflow requires it and confirm profile information.
- Select the correct kingdom or alliance scope.
- Open the page named in the current navigation.
- Review inputs and status before saving, submitting, accepting, or publishing.
- Verify the result in the destination view.
When to ask for help
Contact the community manager responsible for the current scope when information is missing or an action is unavailable. Contact platform support only after checking the account, scope, role assignment, feature availability, and visible error.
Related guides
Practical depth
Your recurring path
Maintain membership and activity, prepare event work, review imports, close corrections, reproduce analytics with named filters, make reward rules visible, and confirm member-facing outcomes.
An alliance leader normally carries the broad alliance assignment; a co-leader receives only the actions configured for that assignment. Both remain bounded to the selected alliance unless a separate kingdom responsibility applies.
Worked example and limits
Starting situation: A reviewed screenshot has one conflicting player row. Confirm alliance, event, date, and current event lock. Resolve the one row against the existing result, apply only eligible rows, then verify event history and Alliance Analytics. The state moves from reviewed proposals to an applied batch; the visible output is the corrected history and recalculated total. A co-leader without overwrite or unlock authority must leave the conflict for the alliance leader or kingdom reviewer. Neither role should change scope, create a duplicate event, or delete the player to force acceptance. Report the batch, row, current state, and exact message when escalation is required.