Intelligence Console quickstart
Sign in, open your first role, and walk the hiring flow from a Success Profile to a defensible decision record.
Access
Invite-only, no self-serve signup.
“Ask your Workerbee contact for an invite, or email support@workerbee.ai.”
Sign in
Google Workspace SSO, mapped to your company’s domain. Accept your invite → you’re signed in automatically → land on your console.
What you land on — the Work Graph
The home screen is a live, interactive visualization of your company’s work: departments, roles, people, and capabilities — color-coded company-specific (yellow) vs. baseline (gray).
A first-run company with little data yet gets honest framing here rather than an empty state:
“Most of what these roles require is not evidenced yet, not that your people lack it.”
with concrete next steps — drop resumes for the people you care about first, connect your HRIS for titles and tenure.
The flow — opening your first role
- Hiring → Open roles → Open a role, pick a department.
- Choose how to start it: talk it through with the agent (it asks what the person owns on day one, what strong predecessors had, IC vs. team lead), paste a job description, or import from your ATS.
- Review the proposed Success Profile — job-specific rows in yellow, inherited rows (from company/department/role) in gray. Click a row to change its importance, or ask the agent to adjust it in conversation.
- Publish it. Changes collect in a pending bar until you publish; if you’re not the Console owner, it goes to an approvals queue instead.
- The ranked pool auto-generates — every evaluated person, not a hidden subset. Click the top candidate to see why they rank there, their evidence, and who could backfill them if they move.
- Invite safely — outreach is consent-based; applicants stay anonymous until they accept.
- Pull the decision record.
A five-sheet export snapshot: the Success Profile version used, the full evaluated population, profile history, and the evidence behind the top recommendation — the same audit trail referenced throughout LLM Connectors.
Beyond hiring
The same console covers:
- Workforce / Departments — department-level Success Profiles and coverage %
- Conversations — agent chat, continued from Claude/ChatGPT/Gemini into the Console
- Node pages for individual capabilities — who holds them, which profiles use them, where they came from
- Settings — Tenants, Access, Modules, Dimensions, Permissions, API keys (this is where your MCP Server API key comes from), Connectors, and Activity (a full undo-capable change log)