Aegis / Frostbyte AI - Product Feedback
Frostbyte requests nested role support and granular session timeouts from Aegis Identity
The call was a product feedback session between AegisCloud and Frostbyte. Victor Zheng reported that Aegis Identity's flat role model forces manual permission duplication and complicates SOC 2 access reviews. He also asked for role- or resource-based session timeout policies instead of a single global setting. Sofia Petrov and Rachel Torres acknowledged both limitations, and Rachel committed to submitting the feedback to product and looping in the account manager. Victor said he was not evaluating alternatives and hoped the gaps would be addressed in the next couple of quarters.
How the call went
Victor expressed clear satisfaction with the SSO and MFA rollout and praised Comply v2, while the rest of the call was neutral issue reporting.
Opening
0Close
03 scored turns of 41. Hover a point for the model's reason, or read the transcript.
How the conversation ran?Talk share is measured from speech time in the captured portion of the transcript.
- Questions we asked
- 5
- Questions they asked
- 6
- Turns
- 41
- Longest silence
- 2s
Who was on the call
AegisCloud
Customer
- Victor Zheng?Matched on an initial rather than a full name, so attribution is weaker.
What happened8
The moments the model picked out, grouped by kind. Each opens onto the turns behind it.
Issue raised3?A problem was brought up on the call.
Victor explains that Aegis Identity's flat role model lacks nested role inheritance, so Frostbyte must duplicate permissions manually across roles.
Victor connects the flat role structure to SOC 2 audit pain, saying access reviews do not tell a clean story, and praises Aegis Comply v2's on-demand reporting.
Victor raises a second gap: session timeouts are globally configured, and Frostbyte wants per-role or per-resource timeouts, e.g. 30 minutes for ML training infrastructure.
Commitment4?Someone committed to doing something.
Rachel says there is no committed GA date for hierarchical roles but offers to follow up with product management for a more specific timeline.
Sofia says session policy granularity is likely not on the short-term roadmap and commits to checking rather than guessing.
Rachel commits to writing up both feature requests, submitting them to product, and looping in Frostbyte's CSM.
Rachel agrees to send Victor a summary email covering the discussion, the two feature requests, and next steps.
Expansion signal1?Interest in buying more, or in a broader rollout.
Victor reassures the team he is not evaluating alternatives and wants Aegis Identity to scale with Frostbyte if the gaps are addressed in the next couple of quarters.
What was promised5
| Commitment | Owner | Due | Action type | ||
|---|---|---|---|---|---|
| Follow up with product management to get a committed timeline for hierarchical role support. | Rachel TorresAegisCloud | No date given | follow up?Check on the status of a prior action, open question, or pending deliverable, or chase and reconnect with someone to keep an item moving. | ||
| Formally write up and submit the hierarchical roles and granular session timeout feature requests to product. | Rachel TorresAegisCloud | No date given | project tracking?Create, break down, or update tickets, epics, sprint boards, milestone plans, or roadmaps, including managing project trackers and task lists. | ||
| Loop Frostbyte's customer success manager into the feature requests for visibility on prioritization. | Rachel TorresAegisCloud | No date given | notify or loop in?Inform, flag, copy, connect, or give a heads-up to a person or team for awareness, including internal alerts and handoffs that are not formal escalations. | ||
| Send Victor a summary email covering the discussion, the two feature requests, and next steps. | Rachel TorresAegisCloud | No date given | send artefact?Deliver or transmit a prepared document, report, email, or update to a recipient by sharing, emailing, circulating, or handing it over. | ||
| Check whether role-based or resource-based session timeout policies are on the product roadmap. IdentityImplied only | Sofia PetrovAegisCloud | No date given | follow up?Check on the status of a prior action, open question, or pending deliverable, or chase and reconnect with someone to keep an item moving. |
Left unanswered2
What is the committed timeline for hierarchical role support in Aegis Identity?
AegisCloudProduct RoadmapAre role- or resource-based session timeout policies on the product roadmap?
AegisCloudProduct Roadmap
Themes and issues3
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 | |
|---|---|---|---|
| Identity & Access?Calls about identity, authentication, authorization, and access management including SSO, MFA, and provisioning. | role management | missing role hierarchy | |
| Identity & Access?Calls about identity, authentication, authorization, and access management including SSO, MFA, and provisioning. | session policy | global timeout limitation | |
| Compliance?Calls about regulatory, audit, and security compliance obligations, reporting, and readiness. | compliance reporting | access review noise |
Numbers stated on this call2
Values are shown exactly as they were spoken.
| Claim | As spoken | Metric | Stated by | |
|---|---|---|---|---|
| Number of users at Frostbyte | “about 1,400 users across the organization” | people count | Victor Zheng | |
| Length of time Frostbyte has used Aegis Identity | “about seven months? Maybe closer to eight” | duration | Victor Zheng |
Coaching5
How the AegisCloud side handled the call.
Strengths (3)
Sofia asked probing questions to understand Frostbyte's scale and the specific audit pain before discussing solutions.
Rachel took clear ownership of the follow-ups, committing to formal write-ups, product submission, and a summary email.
Sofia and Rachel were transparent about what they did not know, avoiding invented timelines.
Improvement notes (2)
The team did not ask for the number of roles Frostbyte manages, only the user count, which leaves the scale of manual duplication unquantified.
Discovery?How well the rep drew out the customer's situation.FYINo target date was attached to the product team follow-up, so Victor has no committed timeline to watch for.
Next step secured?Whether the rep locked in a concrete next step.FYI
How far to trust this call
Every fact above was extracted from the captured portion of the transcript only.
8 min captured of 39 min stated. Anything said in the remaining 31 min is absent from this page.
0 turns flagged low-confidence.
- Clocks unaligned(warning)
2 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 18.8% of a 39.4min meeting; 31.3min after the final turn is unaccounted for
The model's own note: Transcript is partial; covers only the first portion of the call.
Extracted 2 Aug 2026 by deepseek-v4-flash · extractor v1.0.0 · schema v1.1.0 · extended thinking on · 18,410 tokens