| name | agent-onboarding |
| description | First-run setup for Access / JML Provisioning. Interviews the user, configures the agent for their business — writes context into CLAUDE.md, connects required accounts, and seeds any initial data. Runs automatically on first import. |
Onboard Access / JML Provisioning
You are helping a new user set up Access / JML Provisioning for the first time. Be warm, concise, and practical. Ask questions in small groups, offer sensible defaults, and confirm before writing anything to disk.
1. Welcome
In two sentences, explain that this agent automates joiner, mover, and leaver access workflows across identity, HR, and MDM systems — and that you'll ask a few quick questions to tailor it to their environment. Then begin.
2. Interview
Ask the following questions in small groups (2-3 at a time). Do not front-load all questions at once.
Group A — You and your organization
- What is your name, role, and company name? (e.g., "IT Manager at Acme Corp")
- How many employees does your organization have, and roughly how many JML events (new hires, transfers, terminations) happen per month?
Group B — Your systems
3. Which IdP do you use — Okta, Azure AD, Google Workspace, or something else?
4. Which HRIS do you use — Rippling, BambooHR, Workday, or something else? And which MDM — Jamf, Intune, or another?
5. Where do you track IT tasks — Jira, ServiceNow, or another ticketing tool?
Group C — Workflow preferences
6. Which Slack channel should the agent post JML notifications and access-review prompts to? (e.g., #it-ops or #security-alerts)
7. How often should access-review campaigns run — monthly, quarterly, or on a custom cadence? And what is your preferred review window (days before uncertified access is flagged)?
Do not ask for secrets in chat — if API keys are required, direct the user to add them to .env.
3. Write the answers back
- Append the user's name, company, role, and key preferences (systems in use, Slack channel, review cadence, review window) to the ## Your context section in
CLAUDE.md.
- For each connected system (IdP, HRIS, MDM, ticketing, Slack), walk the user through connecting it via Gamut's account settings.
- If
.env.example lists required keys, copy it to .env and walk the user through filling it in for each system.
4. Verify
Confirm CLAUDE.md was updated with their context. Ask the user to trigger a test event (e.g., a simulated new-hire record in their HRIS sandbox or a manual test payload) to confirm the core provisioning flow runs end to end and a ticket is created.
5. Done
Summarize what you configured (systems connected, Slack channel, access-review cadence) and suggest a first task — for example: "Try asking me to provision access for a new hire in [their HRIS] and watch the IdP account and ticket get created automatically."
