Initial Site Configuration

Complete each section below to configure your deployment. Changes are saved per-section and take effect immediately.

🗄️

1 · Database Connection

Connect to the SQL Server database running on your SynapseOps Runner.

⚠️
Runner must be deployed first This connection tests against your Runner container's SQL Server. The test will fail if your Runner hasn't been deployed yet — you can save the values now and re-test after deployment.
This SitePHP app
→
Runner Containeryour server / VM
→
SQL Serverport 14333
→
SynapseOpsWarehousedatabase
The runner endpoint shown on your portal deployment view
Find this in your portal: Licence & Warehouse Settings → WAREHOUSE SSA PASSWORD
🔐

2 · Entra ID SSO & Access Groups

Configures Microsoft Entra ID single sign-on and maps Entra security groups to roles within the application.

ℹ️
This section has two parts: App Registration (for SSO login) and Security Groups (for role-based access). You'll need your Azure Active Directory open to complete this.
Part A — App Registration (SSO Login)
In Entra ID (Azure AD), go to App registrations → New registration and create a new app for this site.
Under Authentication → Add a platform → Web, add this site's URL as a Redirect URI (e.g. https://yoursite.com/index.php).
Under Certificates & secrets → New client secret, create a secret and copy its value immediately.
Under API permissions, add Delegated permissions: User.Read, GroupMember.Read.All and Directory.Read.All, then Grant admin consent.
Copy your Tenant ID and Application (Client) ID from the app's Overview page.
Must exactly match the redirect URI registered in step 2 above
Part B — Security Groups (Role-Based Access)
ℹ️
For each group, enter the display name (how it appears in Entra) and the Object ID (found on the group's Overview page in Entra ID). The app will check group membership at sign-in.
🎨

3 · Branding, Theme & AI Policy

Customise how the site looks and define the AI usage policy shown to your users.

Site Identity
Shown in the browser tab and page headers
Subtitle shown on the main app dashboard
Sets industry-specific terminology and example prompts throughout the app
PNG, JPG, SVG, GIF or WebP — recommended max 300px wide
AI Policy
ℹ️
How the AI Policy works The policy is shown to users before they can access the AI features. Enter your policy content as plain text below — it will be wrapped in the site's styled policy page and saved as ai_policy.html.
The heading displayed at the top of the policy page
Enter your policy as plain text. Use blank lines to separate paragraphs. The content is saved to ai_policy.html.
DRAFT watermark is currently visible
The policy page shows a large "DRAFT" overlay until you turn this off. Disable once your policy content is finalised.
🤖

4 · AI Foundry Provisioning

Runs aifoundry.bash to create or verify the Azure AI Foundry project and update model endpoints in .env.

ℹ️
Already pre-configured for most deployments If you received this template via the SynapseOps portal, the Azure AI Foundry details were pre-filled in your .env during provisioning. You only need to update these if you're pointing to a different Azure tenant or subscription.
This executes a server-side script — review the output carefully
📐

5 · Generate Schemas & Data Sources

Introspects every table in the connected database and generates per-source schema files, likely joins and AI-ready data-source descriptions based on your selected industry.

⚠️
Requires a working database connection (Step 1) Complete and test the database connection before running this step. The example schema files are removed once generation succeeds.
4 data sources currently detected
📧

6 · Email Settings

Configure SMTP for outbound email notifications from the application. Defaults to Office 365.

Used for system alerts and admin notifications
🎉

7 · Complete Setup & Launch

Once all sections above are saved and tested, finish setup to open the application. This marks setup as complete in .env and redirects to the main app.