The setting
develops an AI answer engine that searches the web and replies with cited sources. is the version for large organizations, including regulated industries, with administrator controls over access and use.
Complete audit exports depend on changing pagination without changing the administrator’s script.
A stable ordering protects completeness, while existing continuation tokens protect scheduled collection.
Who you’d be doing this for
“The reviewer asked where those six events went, and I’ve already run the same export twice.”
Vahid Abbasi · IT Administrator · a character in this brief
Collects audit records for a financial institution’s internal compliance review.
What is at stake
Administrators lose audit events when several records share a timestamp. You need to weigh a compatible pagination patch against a snapshot-based route that changes how exports start.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- complete retrieval vs query cost
- token compatibility vs simpler implementation
- transparent correction vs fixed snapshot semantics
Why Perplexity
Audit logs give administrators evidence of activity across Computer and governed enterprise access.
Written with these in mind
Not your kind of problem? 48 more at Perplexity, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Perplexity. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Member of Technical Staff (iOS Engineer, Computer Growth) (opens in a new tab)
- You'll move fast, run many experiments in parallel, and own the outcome end-to-end, while respecting the constraints mobile brings: release cycles, store review, and version fragmentation.
- Engineering Manager (Enterprise) (opens in a new tab)
- Enterprise control plane: identity and access management, SSO/SCIM, role-based access, key management, admin APIs, policy enforcement, audit logging, data governance, or compliance and residency requirements for regulated industries.
- Supporting regulated-industry requirements, including SOC 2, HIPAA, data governance, and residency, with audit logs and analytics that give administrators visibility into how Perplexity is used.
- Member of Technical Staff (Software Engineer, Enterprise Trust & Governance) (opens in a new tab)
- Design and ship secure, well-documented admin APIs for audit logs, members, groups, roles, and settings.
- Deliver audit logs and change notifications that help administrators investigate activity, track configuration changes, and support compliance.
- Member of Technical Staff (Senior QA Web Engineer) (opens in a new tab)
- Member of Technical Staff (GTM Engineer, Growth) (opens in a new tab)
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on fixing one thing without breaking another.
Publishing events appear in Audit Logs but fail to reach the customer’s SIEM.
You have to restore the evidence trail without loosening the permissions their IT administrator protects.
Authorized report requests are failing at 1.8% after session refreshes.
You must weigh a contained guardrail against an IAM rollback in one release window.
GitHub applications disappear from some discovery reviews after rate limits interrupt audit log requests.
You must weigh a clear partial-data signal against the one release slot available this cycle.
The same setting, from another role
Each is set around Perplexity’s Perplexity Enterprise, written for a different role. They’re separate briefs, not the same scenario.
Regulated IT administrators wait while agreement requests arrive without key context.
You must decide whether the system only proposes routes or also holds incomplete matters for counsel.
Regulated IT administrators cannot yet govern Computer access by role.
You must decide which controls belong in reusable terms and which require customer-specific approval.
A healthcare IT administrator cannot enable Computer until the BAA commitments are settled.
You must choose which agent commitments belong in the signed terms and which cannot be promised yet.