Admin audit log

GridCraft has admins. They're people from OmniaDev with read-only access to user accounts so they can answer support questions, debug a stuck map, or investigate abuse reports. The two rules are simple: admins can't edit your maps, and every action is recorded.

What admins can do

• List users (paginated, with search and tier filter).
• View a user's account info and storage stats.
• Browse a user's maps list, read-only.
• Open a single map for read-only inspection.
• Adjust a user's tier (with an optional duration).
• Promote or demote another admin.
• Delete an account (last resort, e.g. spam, TOS violation).

What gets logged

Every admin action writes a row to the admin_audit_log table:

adminId        the admin who acted
targetUserId   the account they acted on
action         e.g. "view_user", "view_map", "list_maps", "update_tier"
resourceId     the map ID (when relevant)
note           optional free text
metadata       JSON with action-specific details
createdAt      timestamp

The log write is best-effort: if the insert fails (DB hiccup), we print to the server log and let the action proceed. The audit trail is a record, not a permission gate.

Where you see it

Every entry pinned to your account shows up on your dashboard under Account → Admin activity. You see who acted, when, what they did, and any metadata attached. Nothing happens silently.

If you ever notice something on that page you can't explain, email [email protected].