1. Executive summary
University of Norvia operates Intelli Campus, a multi-tenant Campus Copilot application developed on the OutSystems low-code platform. Its user interface, business logic, and retrieval-augmented generation (RAG) capabilities reside in OutSystems, while application data is stored in Azure SQL Server.
Tenant onboarding and platform administration must not remain tightly coupled to a single product or its implementation technology. Norvia therefore requires a standalone application named Norvia Backoffice, built on .NET, to provide a technology-neutral administrative control plane for tenants, tenant administrators, Norvia products, product roles, and internal backoffice users.
Business outcome: Norvia can onboard customers and manage access across current and future products without embedding central administration inside Intelli Campus or another product-specific platform.
2. Product context and transformation
This initiative is a controlled separation of administrative capabilities from the existing Intelli Campus product—not a rewrite of Intelli Campus. The current application remains the reference implementation for tenant and user administration behaviour while ownership of those capabilities moves to Norvia Backoffice.
Current stateAdministration inside Intelli Campus
Tenant onboarding, platform roles, and administrator provisioning are coupled to the OutSystems application and its release lifecycle.
Target stateIndependent Norvia Backoffice
A dedicated .NET application owns central administration and integrates with Intelli Campus or another product through a documented API.
The existing Intelli Campus mockup is provided as a product reference for stakeholders and the implementation team. It should be used to understand the source workflows and terminology, while the approved Norvia Backoffice requirements remain authoritative for the new application.
3. Project intent
◎
Create one trusted administrative control plane
Norvia Backoffice exists to remove shared administration from individual products. It gives Norvia a stable place to onboard organisations, define products and roles, manage internal operators, and coordinate product-user provisioning as the product portfolio grows.
The intent is not to reproduce the learner or teaching experience of Intelli Campus. It is to isolate sensitive operational responsibilities behind clear ownership, permissions, auditability, and integration contracts.
CentraliseOne source for tenants, products, roles, and mappings
DecoupleAdministration evolves independently of product releases
ControlRole-based access and auditable operator actions
ExtendFuture products integrate through defined APIs
4. Business objectives
- Decouple tenant and identity administration from the OutSystems application lifecycle.
- Establish a central catalogue of Norvia products and their platform-specific roles.
- Provide controlled, auditable administration for internal Norvia operators.
- Provision tenant administrators through either a product platform API or the course sandbox API.
- Use the shared Azure SQL database as the system of record for tenant and user mapping data.
- Create a foundation that can onboard products implemented in technologies other than OutSystems.
5. Scope and system boundaries
The first release is deliberately limited to the administrative capabilities required to establish products, tenants, roles, and tenant administrators. Product learning features and general end-user experiences remain within Intelli Campus.
| In scope | Outside this release |
| Products and product-role mappings | Product feature configuration and RAG administration |
| Tenants and tenant administrators | Student and general end-user management |
| Independent tenant-admin provisioning | Tenant billing, subscriptions, and licensing |
| Backoffice users, authentication, and authorization | Bulk user imports and self-registration |
| Azure SQL persistence and operational auditing | Rebuilding Intelli Campus functionality in .NET |
6. Users and stakeholders
The application serves a small, controlled operational audience. Customer learners and general Intelli Campus users do not use Norvia Backoffice.
SA
Super Admin
Platform owner with full control of products, roles, tenants, tenant administrators, provisioning, and internal users.
Primary user · Full access
A
Admin
Operations user responsible for customer tenants and their administrators, including provisioning activity.
Primary user · Operational access
U
User
Authenticated internal account with no functional access in this release and a clear restricted-access experience.
Secondary user · Restricted
| Stakeholder | Responsibility and expectation |
| Product Owner | Owns scope, prioritisation, acceptance decisions, and clarification of business rules. |
| Norvia Operations | Uses the backoffice to maintain products, tenants, roles, and administrative access. |
| Product API Provider | Supplies the API signature, credentials, environments, and support for product-specific provisioning. |
| Delivery Team | Implements, tests, documents, and demonstrates the solution against this specification. |
| Role | Permissions |
| Super Admin | Full access to Products, Product Roles, Tenants, Tenant Admins, provisioning, and Backoffice Admins. |
| Admin | View and manage Tenants and Tenant Admins, including tenant-admin provisioning. No access to products, product roles, or backoffice-user administration. |
| User | Can authenticate but has no functional access in this release. The application displays an access-restricted page. |
Authorization must be enforced server-side for every controller/action and must not rely only on hidden navigation items.
7. How Norvia Backoffice works
Norvia Backoffice sits between authorised Norvia operators, the shared development database, and each product’s provisioning interface. It owns administrative records while the product platform continues to own its native user account.
01Norvia OperatorSuper Admin or Admin
→
02Norvia BackofficeValidation, RBAC, audit
↘↗
03Azure SQLAdministrative system of record
04Product APINative account provisioning
Tenant onboarding workflow
1Create tenantCapture organisation and active status
→2Create tenant adminSave the local UserExtended record
→3Review detailsValidate tenant, email, and role
→4Provision userCall the selected product API
Provisioning and identity-mapping workflow
1Validate requestActive tenant and unprovisioned user
→2Send API requestTenantID, UserName, Email, RoleID
→3Receive UserIDProduct returns its native identifier
→4Store mappingWrite UserID to OutSystemsUserId
Ownership rule: Norvia Backoffice owns the local administrative record. The product platform owns the native product account. OutSystemsUserId links the two identities.
8. Functional requirements
F01
Product Management
A product represents an application or service owned by Norvia Labs. The initial product is Intelli Campus, currently implemented on OutSystems.
Associated table: NorviaProducts (ID, Name, Description)
- List all products with name and description.
- Create and update a product.
- Require a unique, non-empty name; description is optional.
- Allow navigation from a product to its configured roles.
F02
Product Role Management
A product role is Norvia’s mapping between a business-facing role name and the actual role identifier created in the product’s implementation platform. For Intelli Campus, ProductRoleID contains the corresponding OutSystems role ID.
Associated table: ProductUserRole (ID, ProductID, ProductRoleID, Name, Order)
- List roles and show product, role name, platform role ID, and display order.
- Create and update product roles.
- Require Product, Name, integer Product Role ID, and Order.
- Enforce uniqueness of
(ProductID, ProductRoleID). - Prevent a role from referencing a product that does not exist.
F03
Tenant Management
A tenant is a customer organization using one or more Norvia products.
Associated table: Tenant (Id, Name, IsActive)
- List, search, create, and update tenants.
- Require a unique tenant name.
- Allow activation and deactivation without deleting historical data.
- Prevent new administrators from being assigned to an inactive tenant.
F04
Tenant Administrator Management
Tenant administrators are customer users stored in the shared UserExtended table and linked to exactly one tenant through Tenant_ID.
List columns: Name, Email, Tenant, View, Provision Status, Provision.
- List, search, create, view, and update tenant administrators.
- Clicking the administrator’s name opens the record in edit mode.
- The View action opens a read-only detail view.
- New records are saved locally before any external provisioning call.
- Provision Status is derived from
OutSystemsUserId: populated means Provisioned; null or empty means Not Provisioned.
- The Provision action remains separate from Create/Update so operators can retry a failed integration without duplicating the local user.
UserExtended fields
Id, OutSystemsUserId, Tenant_ID, Name, Surname, UserInternalID, PhoneNumber, Email, UserRoleID, Address, IsStudent, EnrolledCourse, CurrentYear, CreatedBy, CreatedOn, UpdatedBy, UpdatedOn, IsActive
F05
Tenant Administrator Provisioning
The implementation must support one of the following integration options:
- Product platform-specific API: obtain the API Signature Document from the product API provider, then implement the client according to that provider’s endpoint, authentication, request, response, timeout, error, and idempotency contract.
- Sandbox API: use the supplied
ProvisionTenantAdmin endpoint when the course is delivered standalone and no product platform is available.
Sandbox endpoint: POST https://labs.lowcademy.com/intelli-backoffice/ProvisionTenantAdmin.php
Header parameters: key: 1b43f437-71db-4a41-99fe-3b731257b547 and secret: 61a6ff82-a697-48dd-a760-13e6e69a6586.
JSON request: TenantID (integer), UserName (string), Email (string), and RoleID (integer). JSON response: IsError, Message, and UserID.
- Operator selects Provision for an existing tenant administrator.
- Norvia Backoffice validates tenant, email, role mapping, active status, and current provisioning state.
- The server calls the configured product-specific or sandbox API.
- On success, the returned
UserID must be stored in UserExtended.OutSystemsUserId. - The list immediately displays Provisioned.
- On failure, no identifier is written; the error is logged and a clear retryable result is shown.
F06
Backoffice Administrator Management
Internal users operate Norvia Backoffice independently of tenant accounts.
Associated table: BackofficeUsers (ID, Name, Email, Role, Status, Password)
- Super Admin can list, create, update, activate, and deactivate backoffice users.
- Email is the username and must be unique, case-insensitively.
- Available roles are Super Admin, Admin, and User.
- Passwords must be stored as strong salted hashes and never logged or returned by an API.
- The bootstrap account supplied in the SQL script is for controlled development setup only and must be forced to change its password before wider use.