King or Kingdom Manager

Coordinate cross-alliance views, review kingdom records and rewards, and oversee Castle Position workflows. Keep platform-operator tasks outside public guidance.

Recommended sequence

1. Sign in when the workflow requires it and confirm profile information.
2. Select the correct kingdom or alliance scope.
3. Open the page named in the current navigation.
4. Review inputs and status before saving, submitting, accepting, or publishing.
5. 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

• access and navigation
• access problems

Practical depth

Your recurring path

Maintain community structure, compare alliances from a named scope, coordinate shared access, trace corrections to source records, and publish conflict-checked Castle schedules with visible versions.

Kingdom context can aggregate permitted alliance data and host kingdom workflows, but it does not erase alliance ownership or turn a shared viewer into an editor.

Worked example and limits

Starting situation: Kingdom Analytics shows a low total for Alliance Blue. Preserve the kingdom, event, and date filters, drill into the contributing alliance records, and identify the owning event batch. If a source result is missing, route the correction to an authorized owner rather than editing an aggregate. After correction, verify recalculation with the same filters. The state change occurs at the source record; the kingdom output changes downstream. Kingdom management does not bypass an immutable published revision, a closed Reading Verification assignment, or subscription quota. Escalate with the scope, source identity, filter set, expected total, and observed result, without platform-internal details.

The purpose is community coordination. Troubleshooting stops at user-visible scope, source, state, version, and recovery controls.