Choosing Scope and Understanding Access

Access answers two questions: what may this account do, and in which kingdom or alliance may it do it? Navigation and actions reflect both answers plus current module and subscription availability.

Choose context before acting

Use the available kingdom or alliance selector. Some assignments lock a selector to one community. Recheck it before adding a player, applying an import, entering a result, reviewing Analytics, or publishing Castle Positions. A valid value saved in the wrong community is still wrong.

Changing scope can change navigation, player choices, events, analytics population, premium availability, and row actions. Unsaved form input should not be assumed to move with the selector.

Navigation groups

Workspace contains active records and event views. Discover contains Updates, Knowledge Hub, and Lab. My Tools contains personal results such as rewards or appointments. Input contains manual entry, imports, and reports. Management or settings groups appear only for relevant assignments.

When access is missing

An absent menu item, disabled action, locked premium panel, forbidden page, or empty scoped selector can have different causes. Confirm sign-in, player link, active community, role assignment, subscription feature, module availability, and whether the record is deleted or archived. A direct URL does not override access.

Scope and access landmarks

Read the active community and navigation before opening a shared workflow.

• Account menu and current kingdom or alliance context, including locked selectors.
• Workspace, Discover, My Tools, Input, and any authorized management groups.
• Page banner or context summary that repeats the selected community.
• Forbidden, missing assignment, locked feature, unavailable module, or request-access feedback.

See How Scopes Work and Access Problems.

Purpose, roles, and worked decision

Navigation reflects the account's current scope, applicable stacked roles, feature state, and effective access. Example: A kingdom manager switches to a personal context and Castle planning disappears. The role remains assigned, but the active scope no longer matches the kingdom workflow. Switching back restores evaluation; it does not create or remove the role. A read-only grant may expose Analytics without edit controls. Troubleshoot by recording identity, selected scope, expected role, page, feature label, plan or grant state, and exact disabled wording. Scope selection cannot bypass assignment or suspension.

Understand attention markers

A section's red dot means there is new information or a pending action. Open the section to read What's new here. Informational dots clear after the visible update is seen; genuine review work stays highlighted until it is resolved. The Notifications indicator counts unread updates separately from pending actions.

Use the notification guide if a marker remains after reading. A saved kingdom choice, a name gradient, or a personal subscription never replaces the permission check for a requested action.