Intelli Backoffice

1. Objective

Move tenant onboarding out of OutSystems and demonstrate building a separate .NET application with Codex, deploying it to an Azure VM, sharing the Azure SQL database, and integrating with OutSystems through a secured API.

2. Users

• Super Admin: manages tenants, tenant admins, and other backoffice administrators.
• Backoffice Admin: manages tenants and tenant admins.

3. Functional scope

Tenant Management

• List, search, create, edit, activate, and deactivate tenants.
• Create records directly in the shared Tenant table.
• Tenant name must be unique.

Tenant Administrator Management

• Create the first or additional administrator for a selected tenant.
• Create the profile in the shared UserExtended table with the selected TenantId and a Pending provisioning status.
• Call the secured OutSystems provisioning API to create the platform user and assign the IntelliCampus administrator role.
• Update UserExtended with the returned OutSystems user ID and provisioning result.
• Show provisioning success or failure; never silently report success when the API fails.

Backoffice Administrator Management

• Super Admin can list, create, edit, activate, and deactivate Norvia backoffice administrators.
• These users are stored in BackofficeUser and are not IntelliCampus tenant users.

4. Pages

1. Tenant Management
2. Tenant Administrator Management
3. Backoffice Administrator Management

5. Acceptance criteria

• Every tenant admin is linked to exactly one tenant.
• The OutSystems user ID is saved after successful API provisioning.
• Failed provisioning is visible and can be retried safely without creating duplicates.
• Only authorised Norvia backoffice users can access the application.
• Secrets are held in Azure VM configuration, never in source code.
• All create/update operations are audited.

6. Out of scope

• Tenant billing and subscriptions.
• Bulk user import.
• IntelliCampus feature administration.