Authgnosis clients now have a secure private portal where they can see where each phase of the work stands and download finished deliverables provided as documents. Work delivered as development activities is recorded separately in a private GitHub repository that the client owns, documenting all work activities with a full audit trail for the work. Each page is built from the project tasks in the contracted Statement of Work recorded in the Authgnosis CRM, so the client sees the same plan, hours, and dates Marissa works from.

• Client staff sign in with their own Microsoft or email account as invited guests, and access is checked at three points: Microsoft Entra refuses anyone not invited to the portal; each client's pages and files are open only to that client's people; and the download service checks the person's access and the approved file list again before it reads any file. Each client's page is built on its own, holding only that client's data, and a signed-out visitor or a guest from another client gets the same "not available" page whether or not the page exists. Passwords and keys live only in Azure's protected settings, never in code, with their expiry dates tracked. Before launch the portal was tested signed out, signed in as a different client, and with altered, encoded, and case-changed web addresses, and every attempt was refused.
• Each page shows the engagement's phases with planned and actual hours, progress, target dates, and the status of every task, including the ones waiting on the client's input or approval. A page changes only when Marissa reviews and approves the rebuild, so nothing reaches a client unreviewed.
• Finished deliverables (reports, spreadsheets, and presentations) are listed under the phase they belong to, served only to signed-in members of that client, and checked before they are added: document properties, comments, hidden content, and links. Every client download is recorded in the CRM as a note on the person's contact record and raises a task for Marissa, which she closes as her acknowledgement; a repeat download of the same file that day adds a note but no second task. If the record cannot be written, the download is refused rather than served unrecorded, and the portal writes to the CRM through its own limited identity, which can add notes and tasks and cannot send email or create meetings.
• The portal runs in Authgnosis's own Azure subscription as a separate site at clients.authgnosis.com, not inside the WordPress website hosted on WP Engine. A single DNS record connects the subdomain, and the website's menu carries a Client Portal link to the sign-in page. The portal uses the website's colours, type, and logo, so moving between them reads as one site. The WordPress site, its WP Engine hosting, and its edge security were left unchanged, and no client data passes through WordPress.