Product guide · for whoever runs a training session or watches Team progress

Running onboarding with the Training portal

The Training portal (onboarding.nexusblack.ai) is the joiner's self-guided first week. This guide is for the person who runs a training session, the manager who checks progress, and the admin who keeps the content right.

1. 1. What a session covers
2. 2. How progress is recorded, and who sees it
3. 3. How a joiner gets an account
4. 4. The Portfolio Plan and "Plan built"
5. 5. Changing the words
6. 6. Known limits
7. 7. Owners

1. What a session covers

A session walks the nine modules in order, and a joiner can do the same alone. The rhythm that works: People (who is who, then the customers), Projects (what is being delivered, and to whom), Process (how work flows), Product and Technology (what we build and with what), then Tools and Logins (what the joiner does next on their own laptop). Welcome and Finish frame it.

The Downloads card on Welcome holds three decks (Nexus Black Onboarding, HR Induction May 2026, IT Introduction for APJME and EU). Replacing one is a file change in the repository.

2. How progress is recorded, and who sees it

A joiner presses Mark complete and continue at the bottom of a module. That writes one record: this person, this module, now. Nothing else is recorded: no time on page, no scores, no answers.

• The joiner sees ticks in their own module list and "n of 9 complete".
• A manager (anyone the roster lists as someone's line manager) sees Team progress in the header: their reports, each with the count and a dot per module.
• An ignitionAdmin sees Team progress for everyone Active or Incoming.
• Nobody else sees anything, and there is no export. The record lives in the same database as the roster.

3. How a joiner gets an account

Sign-in is by invitation only: the Clerk application is set to Restricted (Manan Shah, 11 September 2026). Two routes, both through Ignition:

After sign-in the portal applies the two gates: the roster (Active or Incoming, IFS address) and the start date (Incoming joiners wait until the day). A person with an account but no roster row sees "Nexus Black staff only". Keeping the roster right is what keeps the portal right.

4. The Portfolio Plan and "Plan built"

The Projects module draws every customer engagement from the records PMBot keeps. PMBot is not a service; it is a scheduled task (three times a day on weekdays) that writes one file per engagement to the tracking branch of the product-base repository. The portal reads those files, so the plan is as current as PMBot's last run.

The line under the Projects heading is the promise about freshness. Read it like this:

Admins see a Refresh now button under the line, the time of the last attempt, and a note of how the plan compares with PMBot's own page.

5. Changing the words

Module text lives in the repository under data/onboarding/ and reaches the portal on the next Ignition build, or when an engineer runs the content seed. The per-tool "what you do next" wording on Tools and Logins is in code; the "on hold" notices come from the systems Registry in Ignition, so an admin can lift one without an engineer. Charlie Toprak owns the module content with the function leads.

6. Known limits

• Clerk development instance. Both portals sign people in through the development instance of the Clerk application "Nexus Black". It shows a small "Development mode" badge and is capped at 100 users. Nexus Black has about 80 people, so the cap is real. Moving to a production instance is Manan Shah's; when it happens, accounts do not move, and everyone is invited again.
• The roster is the access list. Anyone with an account and a roster row that is Active or Incoming gets in; anyone else is refused. A wrong row, not a broken portal, is the usual reason someone cannot get in.
• Invitations only. Nobody can sign up by themselves, and the portal cannot send an invitation; Ignition does.
• The plan depends on a credential that expires (12 September 2027). The red box above is what expiry looks like.
• Team progress is counts only. No detail on how a module went, and no export.

7. Owners