Environments & Authentication

Primary Environments

LIVE, SUPPORT, STAGING and TEST are all available for you to use.

  • LIVE is available to users 24 hours a day.

  • STAGING and TEST are available 6am - 10pm EST.

  • TEST is only available if you have a VPN Connection to Catch-e running.

URLs

Password Resets

  • In LIVE, use the Reset Password process to reset your password if it has been forgotten.

  • The Reset Password process will not work in other environments, as they do not send emails.

  • For Support, Staging or Test, ask a System Administrator to update your password.

  • If locked out, ask a System Administrator to unlock your account.

Emails

  • Except for specific short testing windows, emails will only generate from the LIVE environment.

  • Go to the Email UAT Checklist page for suggested UAT steps for new or changed emails.

Scheduler

  • Scheduler jobs only run in the LIVE and TEST environments (except short testing windows).

Environment Details

LIVE

This is your main operating environment where business is transacted and users spend most of their time.

URL:
https://demo.catch-e.net.au/bo.phpo?

SUPPORT

This environment is a nightly copy of your LIVE data.

  • Used as a “playground” for safe testing

  • Same login as LIVE

URL:
https://demo.support.catch-e.net.au/bo.phpo?

STAGING

This environment is a point-in-time copy of LIVE data.

  • Used for testing changes with realistic data

  • Same login as LIVE (password changes do not carry over)

URL:
https://demo.staging.catch-e.net.au/bo.phpo?

TEST

This environment is used for testing new developments.

  • Data is not copied or kept up to date

  • Used for UAT and development testing

  • Requires VPN

  • Separate login may be required

URL:
https://demo.test.catch-e.net.au/bo.phpo?

Disaster Recovery (DR)

  • Continuous copy of LIVE system

  • Used only during LIVE outages

  • Users are moved here if LIVE fails

  • Same login as LIVE

  • Not normally accessible unless activated by Catch-e staff

Backup Recovery

We also run:

  • SNAPSHOT

  • REPORTING

  • PRINT (PDF rendering and graphics processing)

SNAPSHOT contains a daily database snapshot for off-site reporting or backup purposes.

Multi Factor / 2 Factor Authentication

Drivers and Employees can enrol in 2 Factor Authentication if enabled.

Enrolment

Fields

  • Code 1 (Number)

  • Code 2 (Number)

Buttons

  • Enrol — Click to enrol in 2FA (only if not enrolled)

  • Unenrol — Click to remove 2FA (only if enrolled)

Setup

2FA strengthens access security.

Configuration

  • Set in Roles / Details

  • Can be Mandatory or Optional per role

  • Not available for:

    • webservices

    • passwordreset

    • fbt_declaration

Methods

Auth App

  • Use RFC 6238 compliant apps (Google Authenticator, Microsoft Authenticator, Authy)

  • App generates 6-digit code every 30 seconds

  • QR code is provided during setup

SMS

  • Requires SMS Global setup

  • Code sent via SMS

  • Valid for 5 minutes

  • One mobile number per user

Global Controls

  • Enable/disable 2FA system-wide

  • Set token name (app label)

  • Configure “remember login” duration

  • Configure SMS provider (smsglobal + API key/secret)

Behaviour

  • Users may be remembered for a set number of days

  • Changes in browser/device/IP may require re-authentication

  • Wi-Fi IP changes may break “remember me”

Users

  • Mandatory: users redirected to 2FA setup on login

  • Optional: users can self-enrol

Admin users can manage enrolment via:

  • Users / 2 Factor Authentication tab

Lockout

  • 3 failed attempts locks user

  • Status changes to “locked”

  • Admin can reset to “active”

Drivers & Employees

  • Can be enrolled or unenrolled via:

    • Drivers / Contact

    • Employees / Contact

  • Uncheck “2FA Enrolled” to remove

Franchise Portal

  • Behaviour depends on:

    • 2FA enabled flag

    • Mandatory flag

    • Enrolment status

  • Enrol/Unenrol buttons may be hidden depending on configuration

Troubleshooting

  • Visit main Troubleshooting page for guidance

  • Session cross-over may occur if multiple sessions are open

Issue Temporary Password

Conditions:

  • Admin role required

  • Feature enabled

  • User must be active

Password Reset (Manual)

Not recommended.

Instead use temporary password feature.

Steps:

  • Go to Users / Password

  • Click Reset

  • Enter new password

  • Save

  • Inform user

User behaviour after reset:

  • Logs in normally

  • Not forced to change password

  • Can change later via Users / Password