Get Started with Juvare Exchange (JX)
This topic will help you successfully set up and share boards and incidents using Juvare Exchange (JX). It outlines prerequisites, step-by-step instructions, and best practices to ensure a smooth onboarding experience.
Overview
JX enables cross-jurisdictional chat sharing via shared boards and incidents. Clients are responsible for their own configuration and participation, while Juvare provides technical support as needed.
Preconditions
You must have WebEOC Full Administrator access to complete the setup.
-
You must confirm that you are on, at a minimum, WebEOC 9.22+ or WebEOC Nexus10.10.1+. For help finding your WebEOC version number, see View WebEOC Version Info. For help finding your WebEOC Nexus version number, see View WebEOC Nexus Version Info.
-
You must have signed the Juvare Exchange (JX) End User Subscription Agreement (“EUSA”) for JX to be installed. If you have already signed the EUSA, please contact your Client Success Manager (CSM) for assistance.
-
When requesting JX installation, you must provide:
-
Organization Name
-
Organization Description
-
Organization contacts that will serve as the JX administrators
-
(Optional) Organization logo, which must be no larger than 2MB in size and in a JPEG or PNG format
-
(Optional) Organization address
If you are unable to provide the optional information during setup, you may edit this yourself afterward. Once an administrator has been set up, they may add additional contacts to their JX network. See Update Your Organization Profile for details.
-
Steps
Step 1: Prepare for Board Sharing
-
Identify participants and draft data sharing agreements that follow any policies or guidelines that your organization may have for data sharing. This is your responsibility. Once data is shared, it cannot be retracted – ensure appropriate safeguards and internal approvals.
-
Determine which boards will be shared, and whether modifications (for example, read-only views) are required.
-
Ensure internal stakeholders agree to sharing rules.
Step 2: Create the JX Network
Follow these steps to create a network.
Networks are limited to clients in the same hosting region. For example, U.S.-hosted clients cannot create a network with Canadian-hosted clients. In FedRAMP or IL5 environments, participants must reside within the same enclave.
Step 3: Publish Boards
Follow these steps to publish boards, also called sharing.
Step 4: Subscribe to Shared Boards
Follow these steps to subscribe to a shared board.
Follow these steps to unsubscribe from a shared board.
Step 5: Share and Subscribe to Incidents
Follow these steps to share an incident.
Follow these steps to subscribe to a shared incident.
-
You can only link one shared incident to one local board at a time.
-
Subscribers can map to an existing local incident or create a new one.
Repeat this process for each new incident.
Step 6: Verify Your Set Up Works
-
Recommended: Create a test board and network to validate configuration before live data is used.
-
Ensure the board is visible to participants, and data flows as expected.
-
Confirm incident subscriptions are correctly mapped.
-
We recommend sending a test board and record from a publisher to a subscriber to confirm that the configuration is correct.
Best Practices & Resources
-
Naming Conventions: Add “JX” and your organization’s name to board and incident titles (for example, “JX - GA EMA Shelter Board”) to help subscribers identify them easily.
-
Default Permissions: Start with “Private” to test functionality. Once validated, adjust sharing settings as needed.
-
Avoid Over-Sharing: Once shared, data cannot be retracted. Review sharing rules carefully before publishing.
-
This help center contains the full JX and WebEOC Nexus documentation—including admin tools, configuration references, and release notes. Ideal for technical users setting up or troubleshooting JX environments.
-
Training Center: Enroll in self-paced courses for JX, WebEOC, and WebEOC Nexus at learning.juvare.com. Designed for both new users and experienced administrators seeking structured training.
Support
For technical support, submit a ticket through your standard support process. Your Client Success Manager (CSM) can assist with guidance, but most tasks must be completed by users with WebEOC Full Admin access.