← Open UI mockupView user stories →
Software requirement specification

Intelli Onboard

A secure, multi-tenant .NET application used by tenant teams to create student identities, student profiles, and supporting-document records while storing document files in Azure Blob Storage.

Fixed ProjectHash: c47d09d0-29c6-4b4e-9a0c-aa7f849baea4

1. Purpose and scope

Intelli Onboard enables authorised staff to onboard a new student for their own tenant. Every read and write is tenant-specific. A successful submission creates the application user in UserExtended, creates the one-to-one Student profile, uploads each accepted file to Azure Blob Storage, and stores searchable file metadata in StudentDocument.

Roles

RoleAccess
Tenant_AdminFull access to all Intelli Onboard functionality within the authenticated tenant.
Tenant_UserCan access Login and Onboard Student and create student onboarding records within the authenticated tenant.

2. Multi-tenant security boundary

3. Login

4. Onboard Student page

FieldRule
Name, Surname, EmailRequired; trim and validate. Email must satisfy the agreed tenant uniqueness rule.
MobileOptional; normalise and validate when supplied.
Father Name, Mother NameOptional student profile fields.
UID NumberOptional unless the tenant policy requires it; unique within the tenant when supplied.
Password, Retype PasswordMust match and satisfy password policy. Hash before persistence; never store or log plain text.
Upload DocumentsMultiple files. Allow-list extensions/MIME types, enforce per-file and request limits, sanitise display names, and virus-scan if available. Show every selected file with its size and a Remove action so an incorrect selection can be removed before submission.

The server must use one database transaction for UserExtended and Student. Blob uploads and metadata writes need compensating cleanup so a failed request does not leave orphaned blobs or partial document records.

4.1 Find and Update Student

5. Data model

EntityRequired design
UserExtendedExisting user record. Save TenantId, name, surname, email, mobile, secure password identity reference/hash, active status, audit fields, and other existing required fields.
StudentUserExtendedId is the primary key and foreign key, enforcing a one-to-one relationship. Store FatherName, MotherName, UIDNumber, and appropriate audit fields.
StudentDocumentId, UserExtendedId, DocumentName, FileSize, FileType, Extension, FilePath, plus recommended TenantId and audit fields for defence-in-depth and traceability.

6. Azure Blob Storage

Store document bytes in a private Blob container. Generate the logical blob path on the server:

{TenantId}/{StudentId}/{DocumentName-or-unique-id}.{extension}

The requested convention TenantId/StudentId/Document.extension is preserved. Use a collision-safe server-generated blob name while keeping the original name in DocumentName. Store the canonical blob path—not a temporary SAS URL—in FilePath. Access must be authorised in the app and use short-lived SAS URLs or server streaming.

7. Configuration and environments

8. Acceptance criteria

9. Database creation queries

Create the tenant-aware Student and StudentDocument tables with the idempotent SQL Server script. It verifies shared dependencies and checks tables and indexes before creating anything.

10. Azure setup guides