Admin Operations¶

This page is the day-to-day admin reference: where to review submissions, how to approve/reject/delete, the optional Discord forum integration, and the limits that protect your deployment.

The Geofence Submissions screen¶

Admins get a Geofence Submissions screen (under the admin area). It lists every user geofence with its status, owner, region, point count, and timestamps. Three view modes:

Geofences with no region land in a "No Region" group, so nothing is hidden just because it lacks a region. Use the status filter tabs to focus — most of the time you'll filter to pending_review to see what's waiting on you.

Reviewing a submission¶

Open a submission to see its shape on a map, who submitted it, and how many points it has. Then choose:

• Approve — promotes it to a public Koji area. You can set a cleaner public name and (optionally) a region. See the full effect in Private geofences & promotion.
• Reject — declines the request with a short reason. The geofence stays private for its owner.

flowchart TD
    PR[pending_review] --> AP[Approve]
    PR --> RJ[Reject]
    AP --> A[approved — PUBLIC]
    RJ --> R[rejected — PRIVATE + note]

Choosing a region at approval time¶

If your Koji project has regions, the approval dialog shows a region picker, pre-filled with whatever region the submission already had. You can:

• Keep it — leave it as-is.
• Change it — file the area under a different region.
• Clear it — promote it as an ungrouped public area.

If your project has no regions, the picker simply doesn't appear, and the area is promoted ungrouped. You can always organize it in Koji afterward.

Deleting geofences¶

Admins can delete any geofence from the admin screen:

• If it's a private geofence, it's removed from PoracleWeb.NET and from every profile that had it switched on.
• If it's an approved (public) geofence, PoracleWeb.NET also removes it from the Koji project so it stops being a selectable public area.

Optional: Discord forum integration¶

You can have PoracleWeb.NET open a Discord forum thread for each submission, so your admin team can discuss and track decisions in Discord. It's entirely optional — everything works without it.

When configured:

• On submit, a thread is created (titled after the geofence) with a Pending tag and an embed showing the name, region, point count, and a map image.
• On approve/reject, PoracleWeb.NET posts the outcome in the thread, retags it Approved/Rejected, then locks and archives it.

If Discord is unreachable or the channel isn't set, the submission still works — the geofence still moves to pending_review/approved/rejected. The forum post is a convenience, never a blocker.

Limits that protect your deployment¶

These are built in to keep things sane — you don't configure them, but it helps to know them when a user asks why something was blocked:

Duplicate names are handled automatically — if a user picks a name that's taken, PoracleWeb.NET appends a number (downtown 2, downtown 3, …).

Turning the whole feature off¶

If you don't want user-drawn geofences at all, there's an admin site setting (disable_user_geofences) that hides the whole feature — the user My Geofences page, the admin review queue, and the create/submit/import endpoints. Existing geofences keep working; this just freezes new ones. Toggle it from the admin Settings page.