Connector status must explain missing content without exposing the content itself.
Administrators need a useful explanation while permission boundaries and third-party limits remain intact.
Who you’d be doing this for
“Three people asked me where the project file went, and I had no clue whether to wait or reconnect the app.”
Camila Herrera · Operations Manager
Maintains connected work applications for a growing business and fields questions when employees cannot find expected files.
What is at stake
Administrators cannot tell whether missing content is delayed, rate-limited, or unavailable to them. You have to make connector state useful without revealing protected metadata or creating false certainty.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- administrator clarity vs. protected metadata
- broad diagnosis vs. narrow first release
- pipeline truth vs. simple language
- support deflection vs. false certainty
Why Dropbox
Dash depends on connected applications delivering authorized work content into one search experience.
Written with these in mind
Not your kind of problem? 26 more at Dropbox, 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.