Validation errors occurring when Integration is no longer linked

If the integration you set up for GoBright is no longer linked, you might see some of the error messages as on the images below.

In the first example, the users of your organization are trying to login and all of a sudden, they are asked to enter Organization code:

In other examples, the users are trying to perform an action for the room bookings, but they are not able to proceed, and they get some of the following error messages:

These messages occur when the integration is no longer linked in your Portal. You would need to login with a non-integrated Admin account and go to the Admin center > Integrations. Here you can select the Integration and check if it’s still linked. If not, it needs to be re-linked with the service account and then everything should work again.

Example for unlinked integration:

Example for linked integration:

Unlinking an integration can sometimes occur and this usually happens after an adjustment somewhere in the integration data. We most often see it after an update on the integrated side (such as an Azure update), or during manual work by an IT person that affects the integration (such as setting a new password or adjusting a setting, for example).

GoBright then makes contact in the ‘known’ way, but because the contact point differs slightly, the integration becomes unlinked.