The shared authorization path must preserve access continuity without preserving access that was removed.
Enterprise rollout needs one connector path, while long-running sessions must lose authority the moment an administrator removes it.
Who you’d be doing this for
“A paralegal lost access to a matter, then the agent still pulled a document from it.”
Dragos Nistor · Legal Operations Manager
Runs matter research workflows that retrieve permissioned documents through enterprise connectors.
What is at stake
Removed access sometimes still reaches workspace records through resumed sessions. You must weigh rollout timing against proof that every connector fails closed.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- enterprise rollout timing vs. revoked-access safety
- unified runtime design vs. dual-path continuity
- agent-session continuity vs. immediate authorization change
- trace evidence vs. release certainty
Why Perplexity
Computer depends on permissioned connectors to turn enterprise knowledge into authorized action across long-running workflows.
Written with these in mind
Not your kind of problem? 31 more at Perplexity, or browse every organization.
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.