When users inside of an enterprise plan “request doc maker” privileges, can those requests be sent to the admin to approve or deny, instead of it automatically making them a doc maker and they get tacked on to the price?
I understand the premise for smaller plans, but for the enterprise, it’s harder to scale large workflows and systems without it causing headaches down the line.
Hey @frost3! Welcome to the community!
Admins can manage Doc Maker requests so users are not automatically added as paid Makers.
For paid Superhuman Docs workspaces, when an editor attempts an action that requires Doc Maker privileges, they should be routed through an admin approval flow rather than automatically starting a trial or adding a paid seat. From there, the workspace admin can approve or decline the request.
For Enterprise teams, the best setup is to ensure the workspace uses manual Doc Maker approval. Admins can review pending requests in workspace settings and track them through admin reporting if the team wants to build notifications around them.
So in short: yes, this can be handled through admin approval rather than automatic seat expansion. I’d recommend checking the workspace’s Doc Maker approval settings to confirm it’s configured that way.
Let me know if these steps aren’t working currently, and I can take a deeper dive into your specific use case.
That’s amazing! Thank you for pointing me in the right direction and for your quick response.
My pleasure! Let me know if you run into any roadblocks here.