Admin tools
Most of these tools are only visible to Platform admins. Hiring Signals is also available to Directory admins. Portfolio access is additionally available to MCA users with the right setup. Standard company administrators never see any of them.
Sync Command Center
The Sync Command Center gives Platform admins a single view of the health and run history of every cross-platform sync channel between Build and Match.
When you'd use this: A sync channel shows a warning or error badge, response data from Match hasn't appeared in the Build question bank after the expected window, or you want to manually trigger the session ingest or disassembly import outside the nightly schedule.
The page has three panel groups:
- Automated sync channels — one card per cron channel showing last-run time, records processed, duration, and a healthy / warning / error badge. Platform admins see a Re-trigger button on the session ingest and session import channels.
- Admin-triggered run logs — paginated history of per-template template sync, template import from Match, and assessment deploy runs.
- Entity links health — synced / stale / conflict counts by entity type from
platform_entity_links. Identity links — total cross-platform SSO identities and the last time one was linked.
See Sync Command Center — monitor and retrigger cross-platform sync for the step-by-step guide.
Hiring Signals
The Hiring Signals scraper finds companies actively hiring for roles that align with Skilladder's skill assessment library. It runs automatically on a Monday–Thursday schedule and writes results to the team's Google Sheet, but Platform admins can also trigger manual runs, review scored leads, and export an XLSX workbook directly from the app.
When you'd use this: The team needs today's demand intelligence leads before the automated run fires, or you want to scrape a specific job family or a list of direct JD URLs that came through sales.
The feature has four sections:
- Runs — history of every scrape job with status, lead count, and sheet sync state
- Leads — all leads across runs, filterable and exportable
- Seen Leads — the deduplication ledger; remove an entry here to allow a lead to resurface in future runs
- Sources — job board configuration; add, pause, or edit boards without touching code
Each lead is scored across seven dimensions (D1–D7) and assigned to a tier:
| Tier | Score range | Meaning |
|---|---|---|
| Tier 1 | 16–21 | Immediate outreach |
| Tier 2 | 11–15 | Nurture |
| Tier 3 | 7–10 | Park for later |
Google Sheet sync requires OAuth credentials in the environment. If a run shows sync failed, contact the engineering team — leads are still saved in the app and can be exported as XLSX regardless.
Portfolio access
The Portfolio access tool lets Platform admins control which MCA users can see which companies. It connects an MCA account to the specific companies that person should manage.
When you'd use this: A new managed-service programme is starting and you need to grant the programme manager access to several client companies at once.
Changes here directly affect what an MCA user can see and do across all their assigned companies. Coordinate with the Skilladder provisioning team before making changes on production accounts, especially for active client programmes.
Registration domains
The Registration domains tool controls which email domains are permitted to sign up for or be invited to Skilladder at a platform level.
When you'd use this: A large enterprise client wants to ensure only corporate email addresses can be used — no personal email accounts.
Important distinction: This is a platform-wide setting, separate from any domain restrictions you can apply per company through team invite settings. If you're unsure which applies to a given situation, check with the Skilladder team before making changes.
Changes to registration domains have policy implications. Get approval before adjusting this in production.