Tenant Configuration
The Stricct Travel Connector uses an Azure-based integration platform to transfer booking data from travel systems into Business Central. This platform supports multiple Business Central tenants, each with its own isolated configuration and data.
How Multi-Tenant Setup Works
Each Business Central tenant that uses the connector has its own connection to the integration platform. Data from one tenant is never visible to or mixed with data from another tenant -- the platform enforces strict isolation between tenants.
Configuring a Tenant
Tenant configuration is managed by administrators and is typically set up once when the extension is first deployed:
- Register the tenant on the integration platform. This establishes the link between your Business Central environment and the platform.
- Configure authentication settings so that the platform can securely communicate with your Business Central instance. This includes setting up the API credentials and endpoints that the platform uses to deliver booking data.
- Verify the connection by sending a test file through the platform and confirming it arrives in the AIR Import List in Business Central.
Managing Multiple Tenants
If your organisation operates several Business Central environments (for example, separate companies or subsidiaries), each environment is configured as its own tenant on the platform. Administrators can manage tenant settings through the integration platform's administration interface.
When to Update Tenant Configuration
You may need to update tenant settings if:
- Your Business Central environment is migrated to a new URL or sandbox.
- API credentials are rotated or expire.
- A new Business Central environment is added to your organisation.
Contact your system administrator or Stricct support if you need to make changes to the tenant configuration.