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.
A preview of model restrictions sits between evidence from past activity and expectations about future Computer workflows.
Administrators want confidence before restricting models, while historical requests leave future agent branches unknown.
Who you’d be doing this for
“Yesterday I spent an hour matching model names to activity, and my manager still asked which research tasks would stop.”
Jamila Noori · IT Administrator · a character in this brief
Prepares model policy changes for a financial-services organization considering broader Computer access.
What is at stake
Six of eight administrators compare Computer activity with proposed model restrictions by hand. You must weigh an understandable preview against claims that past requests cannot support.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- historical examples vs predictions of future behavior
- shared evaluation semantics vs isolation from live traffic
- useful activity detail vs administrative access boundaries
- preview breadth vs a first version people understand
Why Perplexity
Computer combines models and agent workflows, so an administrator’s model restriction reaches beyond a single model selection.
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)
- Self-motivated with strong ownership instincts; you propose experiments, ship features ahead of schedule, and drive improvements without asking for permission.
- As a mobile growth engineer at Perplexity, you'll work across the full mobile funnel — install, activation, onboarding, push and lifecycle messaging, conversion, retention, and in-app purchase moments — for Perplexity, Comet, and Computer on iOS.
- Engineering Manager (Enterprise) (opens in a new tab)
- Enterprise Data Plane: Building the connector platform and semantic data layer that give Computer reliable, permission-aware access to enterprise systems and knowledge, including managed authorization, private-system access, and data freshness.
- 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.
- Member of Technical Staff (Software Engineer, Enterprise Trust & Governance) (opens in a new tab)
- Build the permissions platform, with fine-grained roles and permissions for connectors, tool actions, models, and model effort levels, enforced consistently across products and agent workflows.
- 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)
- Cursor, Claude Code) to navigate the codebase, debug issues, and ship small fixes independently
- In this role, you’ll test the web products and work closely with engineers to find, report, and help resolve issues early.
- Member of Technical Staff (GTM Engineer, Growth) (opens in a new tab)
- You'll turn first-party Computer and Enterprise usage into account-level signals.
- Alongside product engineers, you ship production code, instrument the product and run experiments.
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.
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.