Identity Team - Q2 Roadmap
Identity team aligns on Q2 roadmap: JIT/SCIM, adaptive MFA, audit trail
The Identity team met to plan its Q2 roadmap. They identified three major themes: JIT provisioning and SCIM improvements, adaptive MFA policies, and an Identity audit trail tied to Comply. The JIT/SCIM work was estimated at four to five weeks, while adaptive MFA will ship as a beta in Q2. The audit trail was driven by a near-loss competitive deal and a gap in Comply's SOC 2 reporting. The team assigned Mike Romano to break down epics and Jordan Whitfield to share design work.
How the call went
No external-side turns on an internal planning call; sentiment not applicable.
Opening
0Close
0No turn-level sentiment was scored for this call, so only the opening, close, and overall figures above are available.
How the conversation ran?Talk share is measured from speech time in the captured portion of the transcript.
- Questions we asked
- 15
- Questions they asked
- 0
- Turns
- 46
- Longest silence
- 2s
Who was on the call
Customer
- Internal call
What happened12
The moments the model picked out, grouped by kind. Each opens onto the turns behind it.
Issue raised1?A problem was brought up on the call.
Sofia reports a cluster of support tickets around SSO configuration, specifically JIT provisioning.
Commitment2?Someone committed to doing something.
Mike commits to breaking down the roadmap into Jira epics by end of week.
Jordan commits to sharing the attribute mapping designs in Figma tomorrow morning.
Decision5?A decision was reached.
Alex presents three Q2 themes: JIT/SCIM improvements, adaptive MFA, and an Identity audit trail tied to Comply.
Mike and Ananya outline the JIT/SCIM scope: attribute mapping UI, group-based roles, and fixes for three SCIM failure modes.
Jordan presents a redesigned attribute mapping UI with drag-and-drop and inline validation to cut support tickets.
Sofia scopes adaptive MFA as a first iteration using location and device posture, beta in Q2 and GA in Q3.
Ananya details the Identity audit trail data model and Alex confirms the Comply team is enthusiastic about it.
Risk3?A risk to the account, project, or system was surfaced.
Alex notes the Identity audit trail was driven by a near-loss to Fortiguard Pro over IAM events in compliance reports.
Ananya estimates four to five weeks for the JIT/SCIM work and notes the Detect outage makes rigorous testing essential.
The team discusses SentinelShield's adaptive MFA as competitive pressure, mitigated by deeper platform integration.
Recap1?A summary of what was agreed.
Alex opens the planning session, citing Comply v2 momentum and Identity's recent holding pattern.
What was promised2
| Commitment | Owner | Due | Action type | ||
|---|---|---|---|---|---|
| Break down Q2 Identity roadmap into epics in Jira and flag shared infrastructure dependencies. | Mike RomanoAegisCloud | 17 Apr 2026said “by end of week” | project tracking?Create, break down, or update tickets, epics, sprint boards, milestone plans, or roadmaps, including managing project trackers and task lists. | ||
| Share attribute mapping UI designs in Figma and post to Identity channel for feedback. | Jordan WhitfieldAegisCloud | 14 Apr 2026said “tomorrow morning” | send artefact?Deliver or transmit a prepared document, report, email, or update to a recipient by sharing, emailing, circulating, or handing it over. |
Themes and issues5
What the call was about, and the specific issue recorded under each theme.
| Theme | As the model phrased it?The wording the model used before mapping it to the shared taxonomy. | Issue | |
|---|---|---|---|
| Product Roadmap?Calls about the product roadmap, planning, launch, release, and delivery of new capabilities. | product development | jit provisioning and scim fixes | |
| Security?Calls about security threats, vulnerabilities, certificates, and threat intelligence. | security | adaptive mfa beta | |
| Compliance?Calls about regulatory, audit, and security compliance obligations, reporting, and readiness. | compliance | audit trail for compliance reports | |
| Competition?Calls about competitive positioning, win-loss analysis, deal strategy, and evaluating competitors or alternative vendors. | competition | competitive feature pressure | |
| Support?Calls about customer support interactions, escalations, workarounds, and support experience. | support | sso configuration ticket cluster |
Products mentioned
3 mentions
Competitors mentioned
2 mentions
SentinelShield
Evaluating alternativethreat -1
SentinelShield has had something like this for a while
Fortiguard Pro
Evaluating alternativethreat -1
the Fortiguard Pro competitive deal we almost lost
Numbers stated on this call1
Values are shown exactly as they were spoken.
| Claim | As spoken | Metric | Stated by | |
|---|---|---|---|---|
| Estimated timeline for JIT provisioning and SCIM improvements | “four to five weeks” | effort | Ananya Sharma |
How far to trust this call
Every fact above was extracted from the captured portion of the transcript only.
10 min captured of 48 min stated. Anything said in the remaining 38 min is absent from this page.
0 turns flagged low-confidence.
- Clocks unaligned(warning)
3 participant(s) speak before joining — transcript and events are on different clocks. Do NOT derive absolute timestamps by joining these two sources.
- Partial transcript(warning)
transcript covers 19.2% of a 47.6min meeting; 37.7min after the final turn is unaccounted for
The model's own note: Transcript is partial; recording ends after ~10 minutes of the meeting.
Extracted 2 Aug 2026 by deepseek-v4-flash · extractor v1.0.0 · schema v1.1.0 · extended thinking on · 21,810 tokens