Arux can integrate with Bound to help districts manage facility scheduling across both platforms. Bound is an activities management platform that includes facility management tools for scheduling, reservations, and payments for athletic venues and school spaces.
When the integration is enabled:
- Events from Bound can sync into Arux as Facility Requests. This is a one-way integration from Bound into Arux.
- Your district can also choose to enable a two-way integration where requests created in Arux display for locations tracked in Bound.
Either option helps reduce duplicate entry and gives your team a way to review Bound events within your Arux facility approval workflow.
- A specific Bound pricing plan or subscription level is required before the integration can be enabled. Contact Bound to confirm that your district has the required plan for integration access.
- All integrations with Bound are included in your current Arux agreement.
- If a two-way sync is desired by your district, Arux will work with Bound on the details and functionality of data flowing from Arux to Bound.
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 if you want to enable two-way sync)
- Activating the integration and confirming your desired setup timeline
- Providing a CSV file of Bound spaces for your district to review
Linking Bound Locations to Arux Buildings and Rooms
Before events can sync with Bound, locations must be linked to the correct Buildings and Rooms in Arux.
As part of the setup process, Arux Support or Customer Success will provide a CSV file of spaces from Bound for your district. The CSV will include details such as:
- Space Name
- LocationID
- Location Name
- Location Address
- Location City
Your team will use the CSV to identify which Bound locations should be linked to Buildings and Rooms in Arux.
During this review, your team will need to:
- Find the matching Building or Room in Arux.
- Add a new Building or Room in Arux, if the location should be managed there.
- Modify any existing Buildings or Rooms that should be linked to bound.
- To Modify the Building or Room:
- Select Facilities > Buildings or Rooms.
- Select the desired Building or Room.
- Click Modify.
- Scroll to External Location Identifiers.
- Click Add Partner Link.
- Select the Partner as Bound and enter the External Identifier.
- Click Save.
- To Modify the Building or Room:
- When possible, link any locations you want to have integrated between Arux and Bound. You can choose to skip locations that do not need to sync into Arux, such as unmanaged locations or offsite spaces.
- Add the Bound LocationID from the CSV to the
Building or Room in Arux.
- 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.
- 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.
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 event start date for events that should sync from Bound into Arux.
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.
Events 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 finds a matching 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.
- The Bound tag helps identify Facility Requests that were created or updated through the Bound integration.
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.
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 is enabled, events created directly in Arux will not sync back to Bound.
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?
No. 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.
Automatic approval options for requests created through the Bound integration are currently being considered as a future enhancement. However, automatic approvals are not currently available, and Arux does not have a confirmed timeline for this functionality.
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.
How does Arux match a Bound event to the correct Building or Room?
Arux uses the Bound LocationID to match Bound events to Buildings or Rooms in Arux. Before events can sync correctly, each Bound location that should create Facility Requests in Arux must be linked to the correct Building or Room.
To link a Bound location to Arux, you may need to add or modify your Buildings and Rooms, or add a new Building or Room in Arux.
The Location IDs that you need to add are included in the CSV file you will be provided with from Arux Customer Success. If you have not received this information, contact your Arux Customer Success Specialist or email help@arux.app.
To modify an existing Building or Room that should be linked to Bound:
- Select Facilities > Buildings or Rooms.
- Select the desired Building or Room.
- Click Modify.
- Scroll to External Location Identifiers.
- Click Add Partner Link.
- Select Bound as the Partner and enter the External Identifier.
- Click Save.
Location names do not need to match exactly between Bound and Arux. The Bound LocationID is used to match events to the correct Building or Room.
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 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.
Before contacting Arux, confirm with Bound that your district has the required Bound plan or package for integration access.