Skip to main content

Site Settings Guide

This article explains what Site Settings are, where to find them, and how each Access Experience setting affects driver behaviour in the BaseUp app. These settings control how users experience access, help messages, and support flows at a specific site.

1. What are Site Settings?

Site Settings define site-specific behaviour for access, messaging, and support within the BaseUp app. They allow administrators to tailor the access experience to match site rules, configuration, and operational requirements.

Site Settings help answer questions such as:

  • What happens when a driver first arrives at a site?

  • What message does a driver see if they have access issues?

  • Who should a driver contact if something goes wrong?

  • How does passback behave for different booking types?

2. Where to find Site Settings

To access Site Settings:

  1. Log in to the BaseUp Admin Portal.

  2. Navigate to Configuration > Settings.

  3. Select the relevant Site from the site selector.

  4. Open the Access Experience tab.

All settings described below apply only to the selected site.

3. Passback State settings

Passback controls how the system tracks whether a driver is entering or exiting a site. Correct configuration is critical for access control and preventing misuse.

Initial Passback State for Parking Bookings

Defines the starting passback state for drivers with standard parking bookings.

  • Enter (default): The driver is expected to enter the site first.

This setting should generally remain as Enter unless advised otherwise.

Initial Passback State for Pool Car Bookings

Defines the starting passback state for drivers with pool car bookings.

  • Exit: The driver is expected to exit first (common for pool vehicles already inside the site).

This ensures access events and gate behaviour align with pool car workflows.

4. In‑App Help settings

These settings control what users see when they need help in the app.

Access Screen Noticeboard

A message shown to drivers above the blue Open button on the access screen.

Typical uses include:

  • Site-specific access instructions

  • Temporary notices (maintenance, outages)

  • Entry instructions or restrictions

Booking Details Noticeboard

A message shown to drivers on the booking details screen.

Common uses:

  • Parking location instructions

  • Parking level information

  • Links to maps or instructions

This field supports formatted text and links.

Building Description

A short description displayed alongside the site on the building selector screen.

Use this to help users:

  • Identify the correct building

  • Distinguish between nearby or similar sites

5. Troubleshooting and help content

These settings guide users when something goes wrong.

Troubleshooting Steps

Displayed to drivers on the Get Help screen alongside help options.

Use this to provide:

  • Step-by-step self-help instructions

  • Common fixes before contacting support

Example:

  1. Ensure Bluetooth is enabled

  2. Move closer to the gate

  3. Try opening the gate again


Active Message

Replaces the Open button on the access screen with a custom message.

Common use cases:

  • Temporary access outages

  • Site closures

  • Emergency instructions

Messages should be short and clear. Markdown formatting is supported.

6. Contact Numbers

These settings define who drivers should contact when they experience issues.

Access Issues

The support number displayed to drivers for access-related problems (e.g. gate not opening).

Other Issues

The support number shown for non-access-related issues.

Ensure these numbers are monitored during site operating hours.

7. Remote Trigger - help text

Displayed to drivers when a remote trigger attempt does not resolve the issue.

Use this to:

  • Explain next steps

  • Direct drivers to support

  • Set expectations for resolution

8. Someone is in My Space (Overflow handling)

These settings control what happens when a driver’s assigned space is already occupied.

Overflow Asset Group

Defines which asset group should be used for overflow parking.

Example:

  • Bank Funded – All Bays

Error Message

Displayed to drivers if no overflow space is available.

Use this message to:

  • Explain the situation clearly

  • Provide contact details or next steps

9. Typical configuration flow

A common setup flow for a new site:

  1. Configure passback states for booking types.

  2. Add access and booking noticeboard messages.

  3. Define troubleshooting steps and contact numbers.

  4. Configure overflow handling for occupied spaces.

  5. Test the access experience with a real booking.

10. Troubleshooting Site Settings issues

If users report confusion or access problems:

  • Confirm the correct site is selected.

  • Review noticeboard and active messages for outdated content.

  • Check contact numbers are correct and reachable.

  • Ensure passback settings align with site hardware and workflows.

If issues persist, capture:

  • Site name

  • Booking type

  • Screenshot of what the user sees

For further assistance, please contact the BaseUp support team.

Did this answer your question?