Collaboration & Sharing

Intelligence work is rarely solitary, and the failure mode of team analysis is well known: everyone keeps their own notes, conclusions drift apart, and the team ends up arguing about whose version of events is current. Krataxis is built so a team can work the same situation from a shared source of truth instead of trading screenshots and conflicting summaries.

Two mechanisms make that work: sharing the containers your work lives in, and a collaboration feed that keeps everyone aware of what's changing.

Sharing a battlespace

A battlespace is the natural unit of shared work — it already binds the actors, events, intel, and annotations for one situation, so sharing it shares the whole operating picture in one move. From a battlespace's detail view you can:

• Copy its share link to hand a teammate access. The link is backed by a secure, public-safe token — never an internal identifier — so handing it out never leaks anything about the underlying system.
• Rotate the token to invalidate the existing link when it should no longer work — someone leaves the team, or a link was shared more widely than intended. Rotation works like changing the locks: everyone with the old key is out, and you hand the new key only to the people who should still have it.

Everyone working a shared battlespace sees the same picture, so a brief built from it rests on a common, agreed set of facts.

Share links are access. Treat a battlespace link the way you'd treat a door code. Send it over channels appropriate to the sensitivity of the work, and rotate it whenever the audience changes.

Sharing an investigation

Investigations can be shared the same way. Because an investigation captures its scope, layout, thread of steps, and hypotheses, sharing one hands a colleague not just a conclusion but the whole reproducible line of reasoning behind it — they can reopen it exactly as you left it, check your steps, and carry it forward.

The difference matters. A conclusion alone is like a maths answer with no working shown: you can agree or disagree with it, but you can't check it. A shared investigation is the answer with the working.

The collaboration feed

The Collaboration panel keeps you aware of team activity without having to ask. It surfaces what's happening across the work you share — so when a teammate confirms an event, escalates an item, or updates a battlespace, you're not working from a stale picture. Treat it as the team's shared situational awareness about its own work.

Identity and accountability

Everything you do is attributed to your account and recorded — see Your Profile & Preferences. In a collaborative setting that matters twice over: teammates can see who did what, and the audit record means a shared finding can still be traced to the individual decisions that built it.

That traceability is what lets several analysts contribute to one assessment without it becoming unaccountable. It's the same principle as version control in software or edit history in a shared document: collective work, individual attribution.

Good practice

• Share the battlespace, not screenshots. A live container stays current; an exported image is stale the moment you send it.
• Rotate tokens when the team changes. A share link is only as private as the people who've seen it.
• Hand over investigations, not just conclusions. The value is in the reproducible reasoning, which a shared investigation preserves.

Where to next

• Battlespaces — the container you most often share.
• Investigations — sharing a full line of analysis.