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:
- You accept (the requester accepts automatically when sending).
- The partner accepts.
- Your community has data sharing turned on.
- 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¶
- Both communities turn on the Cross-community sharing toggle in Admin → Data Sharing.
- One side enters the other's handle (the name in its web address, e.g.
san-andreas-rp) and clicks Send Invite. - The other side clicks Accept on the incoming partnership.
- 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.