Open service administration
Administration is for staff with separate system-level access.
How to use it
- Sign in with your administrative account.
- Open Admin in the sidebar or header.
- Review registrations, sign-ins and active sessions.
Advice and practical context
System access differs from a game role
An administrator of one game manages only the permitted capabilities for that project. MARPLA service administration covers the whole service and appears only for staff with separate system-level access. This boundary protects user information and prevents a game role from accidentally expanding into service-wide authority.
Registration, sign-in and active-session summaries provide operating context, but they do not replace inspection of a specific journal event. For public article and guide counters, use the separate Traffic article.
Use the overview to choose the next question
Example: an increase in active sessions may suggest checking sign-in events over the same period. It does not explain the cause or prove audience growth. State the question first, then move to the relevant table and retain the selected range.
Compare measures only when their definitions match. A registration, a successful sign-in and an active session are different events. Do not add them into one figure or use their names interchangeably. When a request concerns one user, use focused search instead of inferring from the overall trend.
Use only the data the task requires
System access exists for support and security, so open only information related to the current case. Do not copy user details into shared documents or publish administration screenshots. A handoff generally needs the case identifier, relevant time and event under review.
A common mistake is treating access to administration as permission for unrestricted analysis. Check the purpose of the section and audience for the result before acting. Never replace an unknown state with an assumption; record the limitation and continue when confirmed evidence is available.
Technical detailsCalculations, permissions and behavior
Separate system access
Admin opens as a regular MARPLA section with the sidebar preserved, while its data remains protected on the server by MARPLA_ADMIN_EMAILS. Workspace owner, game owner and game administrator roles do not grant access. Ordinary users do not see the section and the journal API refuses access.
The allowlist lives only in hosting settings, not in the interface or client code.