The Arux and Bound integration helps districts keep activities scheduling and facilities management connected.
When events are created or updated, information can be shared between the two systems, reducing duplicate data entry and improving visibility for activities directors, facilities teams, community education staff, and community members.
Districts can choose the synchronization model that best fits their workflows:
- Bound Arux: Events scheduled in Bound automatically create Facility Requests in Arux.
- Arux Bound: Facility Requests in Arux are shared with Bound for visibility within activities scheduling.
- Two-Way Sync: Events can be exchanged between both systems.
Community education and activities departments will work together to determine the data flow that works best for them. Your support resources at Arux and Bound will work together to make sure you are all set up.
The integration helps:
- Reduce duplicate data entry
- Improve coordination between departments
- Increase calendar visibility
- Minimize scheduling conflicts
- Maintain accurate facility and event information across systems
- All integrations with Bound are included in your current Arux agreement.
Setting Up a Bound Integration
To get started, email Arux Support at help@arux.app or contact your Customer Success Specialist via email using the subject: Bound Integration.
In your email, include that your district is interested in setting up the Bound integration and is ready to begin the setup process.
After Arux Support or Customer Success receives your request, they will follow up with next steps. This will include:
- Confirming your Bound setup (including which directions you want the data to sync).
- Verifying whether any Bound events have already been manually entered in Arux as Facility Requests.
- Confirming the first Bound event date that should sync into Arux, the first Arux Facility Request date that should sync into Bound, or both dates if two-way sync is enabled.
After Arux Support or Customer Success receives and processes your information, you can continue setup by generating the Bound Location Matching Export from Arux and linking your Bound locations to Arux.
Generating the Bound Location Matching Export Report
Once enabled by Arux Support or Customer Success, you can generate a Bound Location Matching Export report from the Admin Portal:
- Select Reports > All Reports.
- Under Other, select Bound Location Matching Export.
- Select the desired Output Format.
If you have not contacted Arux Support or Customer Success, or if your integration has not been enabled yet the Bound Location Matching Export screen will display a button to Contact Support.
- Click Run Reports.
- When the Jobs menu displays Download Report(s), click it to view, save, or print.
Linking Bound Locations to Arux Locations
Before events can sync with Bound, Bound locations must be linked to the correct locations in Arux. Locations may be linked to a Complex, Building, or Room, depending on how your Facilities setup is managed.
The Bound Location Matching Export includes the Bound locations available for your district which can be linked to Arux locations. Your team will use this report to decide which Bound locations should be linked to locations in Arux.
The report includes details such as:
- Location Name
- Bound LocationID
- Facility Name
- Address
- City
- Arux Locations
- Shared With: Used when multiple Bound locations link to a single Arux location
During this review, your team will need to:
- Find the matching Complex, Building, or Room in Arux, if one exists.
- Add a new Complex, Building, or Room in Arux, if the location should be managed there.
- Skip locations that should not sync with Arux, such as unmanaged locations or offsite spaces.
- Add the Bound LocationID to the matching Arux location using External Location Identifiers.
Not every Bound location needs to be linked in Arux. If a Bound location should not create Facility Requests in Arux, you can skip that location.
Adding a Bound LocationID to an Arux Location
If the desired location does not currently exist in Arux, add a new Complex, Building, or Room if the location should be managed in Arux.
To link a Bound location to an Arux Building or Room:
- Select Facilities > Complexes, Buildings, or Rooms.
- Search for and select the desired Complex, Building, or Room.
- Click Modify.
- Scroll to External Location Identifiers.
- Click Add Partner Link.
- Select Bound as the Partner.
- Enter the Bound LocationID as the External Identifier.
- Click Save.
Repeat this process for each Bound location that should sync with Arux.
- The Bound LocationID is used to match events from Bound to locations in Arux. Location names do not need to match between Bound and Arux.
- A single Building or Room in Arux can be linked to more than one Bound location, if needed.
Verifying Location Links With the Report
After you have linked the Bound locations that should sync with Arux, generate the Bound Location Matching Export again.
Open the report and confirm that the Arux Locations field is complete for each Bound LocationID that should be included in the integration.
After you confirm the location links, respond to the message from Arux Support or Customer Success and attach the updated report. Arux will review the setup and follow up with next steps.
Confirming the Integration Timeline
As part of the setup process, Arux will work with your team to confirm when the integration should begin.
Your team will need to confirm:
- The date when the integration should go live.
- The first Bound event date that should sync into Arux, if using Bound to Arux sync.
- The first Arux Facility Request date that should sync into Bound, if using Arux to Bound sync.
The event start date determines which Bound events will sync into Arux.
Your district may choose to enable the integration before the fall season but only sync events with a start date on or after August 1, 2026.
Records before the selected event start date will not be included unless otherwise discussed with Arux Support.
Syncing With Bound
Once the Bound integration is enabled, Bound sends event information to Arux using the Bound LocationID.
If Arux to Bound sync is enabled, eligible Facility Requests created in Arux can also display in Bound for linked locations.
If Arux finds a matching Complex, Building, or Room with that LocationID, the event will appear in Arux as a Facility Request. If no matching LocationID is found, the event is skipped and a Facility Request is not created.
Requests created from Bound will display with a Bound tag in List Views and View Pages and will automatically be set to Pending Approval. This allows your team to review and approve the request through your normal facility approval process in Arux.
If an event was previously synced from Bound and is later updated in Bound, the existing Facility Request in Arux may be set to Resubmitted for Approval.
- By default, requests created from Bound are set to Pending Approval in Arux. If your district requires automatic approval options for requests created through the Bound integration, contact Arux Support or your Customer Success Specialist.
- If an Arux to Bound sync or two-way sync is enabled, eligible Facility Requests created in Arux can display in Bound for linked locations.
Reviewing Duplicate or Conflicting Events
If your district has already entered the same events in both Bound and Arux, duplicate or conflicting Facility Requests will need to be reviewed.
If an event already exists as a manually created Facility Request in Arux and the same event later syncs from Bound, your team may need to remove or update the manually created request to avoid conflicts.
To help review these records, you can filter Facility Requests by the Bound tag and review any requests that show a conflict.
If a Bound event does not appear in Arux, confirm that the Bound LocationID has been added to the correct Building or Room in Arux.
If your district has already started entering the same events in both Bound and Arux, contact Arux Support before the integration goes live.
Our team can help determine the best approach for reviewing duplicate or conflicting requests.
FAQ
Is the Bound integration one-way or two-way?
The integration between Arux and Bound has the ability to be a two-way integration. When the integration is enabled, eligible events from Bound can sync into Arux as Facility Requests.
If a one-way integration from Bound to Arux is enabled, events created directly in Arux will not sync back to Bound.
If a one-way integration from Arux to Bound is enabled, events created directly in Bound will not sync back to Arux.If a two-way integration is desired, Arux Customer Success can work with your district to discuss options for syncing data from Arux back into Bound.
Do Bound events automatically become approved Facility Requests in Arux?
By default, requests created from Bound are automatically set to Pending Approval in Arux. This allows your team to review and approve the request through your normal facility approval process.
This also gives your team the opportunity to add Setup and Takedown notes or times in Arux, if needed. Bound does not currently include options to send Setup or Takedown information to Arux.
If a Bound event was previously synced into Arux and is later updated in Bound, the existing Facility Request in Arux will be set to Resubmitted for Approval.
If you require automatic approval options for requests created through the Bound integration, contact Arux Support or your Customer Success Specialist.
How does Arux match a Bound event to the correct Building or Room?
Arux uses the Bound LocationID to match Bound events to locations in Arux. Before events can sync correctly, each Bound location that should create Facility Requests in Arux must be linked to the correct Complex, Building, or Room.
For setup steps, see Linking Bound Locations to Arux Locations.
If you need assistance or more information, contact your Arux Customer Success Specialist or email help@arux.app.
Where can my team review Bound events in Arux?
Bound events appear in Arux List Views under Facilities > Requests and Request Parts. Requests created or updated through the Bound integration display with a Bound tag.
You can filter the Facility Requests List View by the Bound tag to review requests created through the integration. This can also make it easier to review and approve Bound-created requests.
For more information on filtering List Views, see the Arux Self-Service Library article on Customizing List Views.
What happens if a Bound LocationID is not linked in Arux?
If Arux does not find a matching Complex, Building, or Room with the Bound LocationID for an event, the event is skipped and a Facility Request will not be created in Arux.
If an event from Bound does not appear in Arux, confirm that the Bound LocationID has been added to the correct Building or Room before contacting Arux Support.
Not every Bound location needs to be linked in Arux. If a Bound location should not create Facility Requests in Arux, you can skip that location during setup.
A single Building or Room in Arux can also be linked to more than one Bound location, if needed.
Can my team choose which Bound events sync into Arux?
There is no way to filter or pick individual Bound events to sync into Arux. Events are added to Arux based on the event start date selected before the integration is enabled.
As part of the setup process, Arux will work with your team to confirm the integration go-live date and the event start date for events that should sync from Bound into Arux.
The event start date determines which Bound events are included. Events before the selected event start date will not be included unless otherwise discussed with Arux Support.
What happens if the same event already exists in both Bound and Arux?
If your district has already entered the same events in both Bound and Arux, duplicate or conflicting Facility Requests may be displayed in Arux and need to be reviewed.
For example, if an event already exists as a manually created Facility Request in Arux and the same event later syncs from Bound, your team may need to remove or update the manually created request to avoid conflicts.
If your district has already started entering the same events in both systems, contact Arux Support before the integration goes live. The Arux team can help determine the best approach for reviewing duplicate or conflicting requests.
How does my district get started with the Bound integration?
To get started, contact Arux Support at help@arux.app or reach out to your Customer Success Specialist with the subject line Bound Integration.