Feature Availability

Not every user sees the same pages. Navigation reflects account status, assigned role, selected scope, subscriptions, and whether a module is enabled.

Availability labels

• Available: the feature can be opened under its normal access rules.
• Available when enabled: a manager controls whether the module is shown.
• Requires authorized access: the workflow belongs to a community role or reviewer.
• Requires a subscription: the current scope needs an active entitlement.
• Limited availability: the feature is in a restricted or beta state.
• Temporarily unavailable: saved information remains, but the tool cannot currently be used.

Current product areas

Core account, scope, player, event, import, analytics, reward, report, Castle Position, Knowledge Hub, subscription support, and Lab routes exist in the current product. Exact visibility depends on access. The documented Lab includes Hero Gear Optimizer, Governor Gear Optimizer, Charm Optimizer, Bear Trap Simulator, Rally Simulator, and Battle Simulator. Beta tools should be treated as estimates.

Knowledge Hub may display a building state. Individual articles may be public, scoped, premium, draft, archived, or unavailable to the current reader.

Related guides

• access problems
• access and usage

Practical depth

Check every access layer

Account state, player link, membership, selected scope, role, plan, grant, allocation, quota, and record status can all affect an action. Passing one layer does not bypass the others.

Purpose, controls, and worked decision

Availability explains why a navigation item or Run control appears, disables, becomes read-only, or enters limited mode. Example: A member has the right alliance role and an accepted grant, but the module is disabled for that scope. Feature availability fails before the grant is used, so the action stays hidden or disabled. Enabling the feature can restore evaluation; the grant still cannot add management rights. Limitations include plan dates, quota, allocation, suspension, and page state. Troubleshoot with feature label, scope, assignment, effective source, usage state, and exact message.