Genus logoG365
Demonstration environment · simulated data · viewing as Alex Morgan (Employee)

Demo guide

Suggested journeys, what is simulated, and how G365 is designed to grow.

Journey 1 — Discover and launch Contract Obligation Tracking

  1. Switch to Sarah Bennett from the profile menu.
  2. On Home, select the Contract Obligation Tracking tile.
  3. Choose Launch Application — the Azure-hosted prototype opens in a new tab.

Journey 2 — Discover and launch Genus Learning

  1. Switch to Alex Morgan.
  2. Note the outstanding training on Home.
  3. Ask Gopilot “Show my outstanding training”.
  4. Select Launch Genus Learning.

Journey 3 — Gopilot assistance

  1. Switch to Sarah Bennett.
  2. Ask “What needs my attention today?”.
  3. Select a Contract Obligation Tracking task to open its G365 detail.
  4. Open in Contract Obligation Tracking.

Journey 4 — Role-aware experience

  1. As Alex, Contract Obligation Tracking is not in My Applications and appears locked in the App Library.
  2. Switch to Sarah — Contract Obligation Tracking appears.
  3. Switch to Priya — compliance oversight appears on Home.

Journey 5 — Application extensibility

  1. Enable demo administrator mode in the profile menu.
  2. Open App Registry → Add demo application.
  3. Set name, icon, category, launch mode and roles, then Save.
  4. Check the App Library, then disable it and confirm Launch is unavailable.

What's real and what's simulated

  • Real: launching Contract Obligation Tracking and Genus Learning at their configured URLs, in a new tab, using their own sign-in.
  • Simulated: personas, tasks, training, obligations, notifications, Gopilot responses and registry edits. Nothing is read from or written to either application.
  • The Genus Learning link is a temporary preview URL. Replace it with the published URL in the App Registry when available.
  • Visual styling is a provisional Genus-inspired system, not verified official Genus brand guidelines.

Future integration architecture

Proposed — not implemented in v0.1

Each application stays independently deployed and owns its data. G365 is the experience layer. Applications could later expose authenticated endpoints such as:

  • GET /g365/manifest
  • GET /g365/tasks
  • GET /g365/notifications

These are illustrative interface examples, not existing endpoints. G365 does not call them.

Security principles

  • · Enterprise single sign-on
  • · Central identity integration
  • · Application-specific authorisation
  • · Least privilege
  • · Auditing
  • · Secure API communication
  • · Data residency
  • · Privacy
  • · Human approval for consequential actions