← Open UI mockupArchitecture & build prompt →
Delivery backlog

Intelli Onboard User Stories

Implementation-ready stories for identity, tenant isolation, onboarding, document storage, deployment, and operational quality.

US-01Authenticate with a product-specific role

As a tenant team member, I want to sign in so that I can access only the Intelli Onboard capabilities granted to me.

  • Validate active UserExtended credentials and resolve TenantId on the server.
  • Use ProjectHash c47d09d0-29c6-4b4e-9a0c-aa7f849baea4 to query UserExtendedRoleMapping.
  • Permit only Tenant_Admin or Tenant_User; reject missing/inactive mappings with a generic message.
US-02Enforce tenant isolation

As a platform owner, I want every operation scoped to the authenticated tenant so that one tenant can never access another tenant's students or documents.

  • Apply TenantId filtering in the data-access layer to every query and write.
  • Do not trust TenantId, StudentId ownership, or role values submitted by the client.
  • Add negative integration tests for cross-tenant identifiers.
US-03Create the user and student profile

As a Tenant Admin or Tenant User, I want to enter student information so that a new student account and profile are created together.

  • Require name, surname, and email; validate optional mobile, parent names, and UID.
  • Validate matching passwords and hash securely.
  • Create UserExtended and the one-to-one Student row in one transaction and show a clear success state.
US-04Upload and correct multiple document selections

As an onboarding user, I want to attach multiple documents and remove an incorrect selection before saving so that only the intended evidence is uploaded.

  • Show every selected filename and size with an accessible Remove action.
  • Removing a selection updates the actual upload payload and does not affect other selected files.
  • Validate file count, size, extension, MIME signature, and safe filename, upload under the tenant/student path, and write one StudentDocument row per successful Blob.
US-05Authorise document access

As a security owner, I want document retrieval to be authorised so that private files are never publicly exposed.

  • Check tenant and student ownership before retrieval.
  • Return a short-lived SAS URL or stream through the authorised application.
  • Audit upload and access without logging sensitive document contents or secrets.
US-06Configure local development

As a developer, I want to use local SQL Server and development-safe Blob settings so that I can build and test without production secrets.

  • Read SQL Server and Storage configuration from standard .NET configuration.
  • Use user secrets/environment variables and provide placeholder templates plus migrations.
  • Document setup and seed only non-sensitive development data.
US-07Deploy to Azure App Service

As a release engineer, I want a repeatable Azure deployment so that Intelli Onboard operates securely in the cloud.

  • Configure App Service, connection strings, Storage access, HTTPS, health checks, and production logging.
  • Prefer managed identity and least-privilege Blob permissions.
  • Follow the downloadable App Service and Blob setup guides and complete a post-deployment smoke test.
US-08Find and update an existing student

As a Tenant Admin or Tenant User, I want to find a student and update the profile so that student information and supporting documents stay accurate.

  • Search by email, UID number, or student ID within the authenticated tenant only.
  • Edit authorised UserExtended and Student fields with validation, uniqueness checks, concurrency protection, and audit history.
  • Add new documents, remove new selections before saving, and remove existing documents with confirmation and safe metadata/Blob deletion.