Manual approval protects seat budgets while obscuring what happens after a Doc Maker request.
Administrators need to control paid-seat additions, while employees need a clear path to request access.
Who you’d be doing this for
“I turned on approval, then got three requests and still had to ask whether we were being billed.”
Greta Johnson · Document Administrator
Manages paid access and approval settings for a large Docs deployment.
What is at stake
Only 61% of administrators finish the seat-approval setup, and many reopen settings after requests arrive. You have to weigh a simpler approval flow against keeping paid-seat control explicit.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- clear self-serve setup vs explicit seat-cost control
- faster trial activation vs trusted approval boundaries
- simple language vs precise billing states
Why Superhuman
Superhuman Docs depends on administrators being able to govern paid access before enterprise teams deploy document workflows.
Written with these in mind
Not your kind of problem? 30 more at Superhuman, 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.