Cross-Community Data Sharing

Allied communities can opt in to share civilian and vehicle records, so a plate or person run in one city surfaces relevant hits from partner cities, with the source community shown. Configure it in Admin → Data Sharing (owners and admins).

How it works

Sharing is a reciprocal partnership. You invite another community by its handle (slug), and data only federates when all of these are true:

1. You accept (the requester accepts automatically when sending).
2. The partner accepts.
3. Your community has data sharing turned on.
4. The partner's community has data sharing turned on.

If your master toggle is off, nothing federates in either direction; your records stay private and you see none of theirs.

Setting it up

1. Both communities turn on the Cross-community sharing toggle in Admin → Data Sharing.
2. One side enters the other's handle (the name in its web address, e.g. san-andreas-rp) and clicks Send Invite.
3. The other side clicks Accept on the incoming partnership.
4. Queries now federate across the partnership.

Each partnership row shows its Direction (Outgoing / Incoming) and State:

State	Meaning
Active	Both accepted and both toggles are on; data is federating.
Needs your OK	You were invited; click Accept.
Accepted	The other side accepted, but it isn't active yet (usually a master toggle is off somewhere).
Pending	Your invite was sent and is awaiting acceptance.

Turn the community-wide toggle off, or click Remove on a partnership, at any time. Remove deletes the partnership entirely (either side can do it); you'd re-invite to restore it.

What's shared

When active, these lookups widen to search you plus your active partners, and out-of-city hits are tagged with their origin:

Query	Federates?
Plate / vehicle returns (owner, registration, insurance, stolen flag)	Yes
Person returns (identity, DL & status, licenses, carry permit, registered firearms, warrants)	Yes
Firearm and boat checks	Yes
Warrant search (active/signed warrants by name)	Yes
Owner warrants attached to a plate/gun/boat return	Yes
Court shared priors (partner convictions counted in sentencing)	Only if enabled in Court

The following stay private to your own community/server and never federate:

• BOLOs: a partner's plate can still return a match, but the BOLO flag reflects only your own server's bulletins.
• CAD call history / CONTACTS, prior calls, address history, and incident search.
• A shared subject's priors list comes from that subject's home community, not merged into yours.

Provenance

Cross-community hits are labeled with the source community. In the MDT person teletype return you'll see a line like (shared record - San Andreas RP), and plate notes added to a call read (shared - <source>). Court rap sheets show partner priors as e.g. (+3 shared).

Counting partner convictions as priors

To have partner communities' convictions count toward sentencing, enable Count data-sharing partners' convictions as priors on the Court tab. Without it, sharing only affects live queries, not sentencing.

Out-of-state hits

A partner's record belongs to another agency's system. Returns say so, and name whose:

• Ownership is the test. Any record your community did not file is marked *** OUT OF STATE RECORD - <STATE> *** directly under the name (a plate reads OUT OF STATE REGISTRATION). Your own records are never marked; they read exactly as before.
• The state named is the owning community's, read from that community's State setting (Admin → Community → Settings), so you know whose system to confirm the record with. This applies even when a partner runs the same state you do: the file is still theirs, not yours.
• The STATE on a plate or DL line is likewise the issuing community's state, not yours.
• A shared subject with a warrant carries an extra line on the WANTS / WARRANTS block: *** WARRANT(S) ISSUED OUT OF STATE - <STATE> - CONFIRM EXTRADITION W/ DISPATCH ***.

Set your community's State if you have not. With it unset, returns can still mark a partner record as out of state, but cannot name which state it came from.

Opening a partner's warrant record

The report number beside a warrant ([#AW-26-0007]) opens that record, including when the warrant belongs to a partner community. A partner's record opens read only: it is marked with the issuing agency and state, and captioned with their court rather than yours. Only filed (approved) records open this way: a partner's drafts, kicked-back and pending-approval reports are never reachable, and their supervisor review thread and edit history stay private to them.