Overview

The system is designed to be multi-client, meaning that it is able to serve multiple clients, with one selected at a time, by means of a filter. This requires an architecture which supports multiple clients wherever necessary in the system and includes:

• Bookings - where live bookings are viewed and processed

• Archive - where archived bookings can be viewed

• Configuration - based setup data specifically for the White Glove process for that client

https://bigdigit.atlassian.net/browse/WG-108

Client Selection

A different client can be selected at any time which will result in the records of that client being shown on the screen. The client cannot be changed during an update process or when a modal is being shown.

Partner Client Email Address

The Partner Client Email address is the “cc” address for any email correspondence to external parties. That should be shown on the banner along with the currently selected client.

Client Filter Selection Persistence

Each time a user logs into the system he should see the client selected in the previous session. Ultimately that would be stored against the user. However during the development process it is acceptable to have the value stored in local storage against a browser. https://bigdigit.atlassian.net/browse/WG-121

Authentication, Entitlements and Row Level Security

Authentication and security will ensure the following:

1. In the main application Partner Users can see only

   1. Clients to which they have authorised access

   2. Only specific screens to which they have authorised access

2. In the Client Portal it allows

   1. Clients to see only their Client records

   2. Only the specific screens to which they have authorised access

Currently only point (2) is important as it is not necessary for the Partner Users to be authorised.

CSV Bookings Upload

Bookings should be uploadable by each individual Client. https://bigdigit.atlassian.net/browse/WG-537. This will probably be done using iHub pointing to the White Glove application.