How Scopes Work

A scope is the kingdom or alliance context in which a task is performed. The same account can have different responsibilities in different scopes.

Scope-sensitive actions

Player creation, imports, event records, analytics, reward review, Knowledge content, reports, and Castle Position management can all depend on scope. Confirm the selector and page heading before acting.

Visibility

Authorized kingdom users may see cross-alliance views. Alliance managers normally work only with assigned alliances. Players see personal or specifically shared information. Changing the selected scope changes the records shown; it does not move records between communities.

Kingdom and alliance scope landmarks

Confirm the community context in both the application shell and the page-level selector.

• Active server, selected kingdom, and available alliance selector as distinct controls.
• Locked selector when an assignment fixes the viewer to one scope.
• Page context banner on Players, Events, Imports, Analytics, or Castle Positions.
• Empty, forbidden, or missing-assignment feedback after a scope change.

Related guides

• platform model
• access and navigation

Practical depth

Check scope before shared work

Read the switcher, page heading, and record owner together. A kingdom view can combine alliances while an alliance view can offer more detailed controls for its own roster. Filters refine a scope; they do not move records.

Controls, workflow, and worked example

Use the scope switcher to choose only available kingdom or alliance contexts, then verify the label before opening or saving shared work. Roles are evaluated within that context. Example: A leader sees two alliances but is assigned to edit only one. Switching changes visible records; edit controls appear only for the matching assignment. The other alliance can remain read-only or unavailable. Scope switching cannot move players or grant access. Troubleshoot with account, selected context, expected assignment, page, and visible message.

The decision output is an active personal, alliance, or kingdom context plus the actions resolved there. Controls never broaden the assignment. Limitations include inactive membership, feature-disabled state, read-only sharing, premium boundaries, quota, and suspension. The safe workflow returns to an available scope rather than forcing a hidden route.