Administration & Systems
Most of the knowledge base is about doing intelligence work. This article covers the surrounding scaffolding — the parts that keep a deployment accountable and connected. Some of it is administrator-only; if you don't see a panel mentioned here, your role doesn't include it, which is expected.
The audit record
Every action that creates, changes, or deletes data is recorded — who did it, what they did, to which entity, and when. That covers sign-in and sign-out, events, units, annotations, sources, layers, areas of interest, and battlespaces.
This isn't bookkeeping for its own sake: it's what makes the platform's output defensible. A conclusion is only as trustworthy as the trail behind it, and the audit record means any finding can be traced to the individual decisions that produced it — through review, audit, or disclosure. The record is append-only, so history can't be quietly rewritten.
User administration
On deployments where you hold an administrator role, the Admin area is where operator accounts and their permissions are managed — provisioning accounts, setting what each role can see and do, and removing access when someone leaves. This is also how deployments that disable open sign-up bring new analysts on board (see Creating an Account & Signing In).
Role-based access is the backbone of multi-team use: read-only analysts, write-enabled operators, and administrators each see an appropriate slice of the platform.
Systems panels
Two operator-facing panels live under ⊞ Tools → Systems:
- Infrastructure — a status view of the platform's own moving parts, so an operator can see at a glance that collection and processing are healthy.
- Webhooks — outbound integration. Webhooks let the platform notify other systems when something happens — pushing an alert or event into a downstream tool, a messaging channel, or your own pipeline — so Krataxis fits into a wider workflow rather than being a walled garden.
These are deployment- and integration-level features; day-to-day analysis never requires them, but they're how an organisation operationalises the platform across its own stack.
Managing data sources
Beyond the feeds individual analysts add (see Feeds & Sources), a deployment runs a set of platform-wide data sources that feed every battlespace centrally. These are administered under Admin → Sources.
The Sources view is a health dashboard: each source's credibility score, how many items it has contributed, how many ingestion runs and errors it logged in the last 24 hours, and when it last ran with what status. It's where an operator confirms collection is healthy — a source quietly erroring out shows here first.
Opening a source for editing exposes its core settings — display name, type, credibility score, poll interval, an active toggle, and a configuration field (JSON) holding the type-specific parameters. You can also poll now rather than wait for the schedule, and attach a source to a battlespace so its reporting is always included there.
The GDELT global-events source
The clearest example is GDELT — the worldwide news-event source described in Feeds & Sources. It ships pre-configured and active, polling every 15 minutes. Its configuration field exposes a few deliberate knobs:
- Event types — which categories of event to keep. The default watches conflict and crisis activity (protests, force posture, assaults, fighting, mass violence); narrow it to cut noise, widen it for broader awareness.
- Location precision — the minimum geographic precision to accept. Left at its default, the source keeps city- and landmark-level events and discards country-centroid guesses, so the map isn't littered with markers parked on a nation's centre point.
- Outlet corroboration — whether to pull the list of distinct outlets reporting each event. With it on, an event's corroboration is seeded from how many independent outlets carried it (see Credibility & Validity).
Because GDELT is a shared platform source, its events are scoped into each battlespace by location automatically — a battlespace covering Eastern Europe picks up Eastern-European events with no per-battlespace setup. To bring a deployment's GDELT picture online you typically need do nothing; to tune it, adjust the knobs above and poll now to see the effect.
Where to next
- Creating an Account & Signing In — how accounts are provisioned.
- Your Profile & Preferences — the per-analyst settings that complement role-based access.