Just upgraded to their team plan. The new features are a start, but the permission model is too thin.
You get Admin and Member. That's it.
* Admin can do everything, including billing.
* Member can only write and use the tools.
* No custom roles. No granular control over workspace/module access.
For a small team it's okay. But if you need to manage client projects or separate internal vs. external content, it's not enough. You're forced to give too much access or create separate accounts/workspaces.
Has anyone found a workaround? Or are we stuck waiting for them to add more levels?
Ship fast, review slower
I ran into this exact issue last month when we onboarded a contract writer. We needed them to work in one client workspace but not see our internal planning docs or billing info.
The separate workspace workaround is messy. It creates data silos and you end up paying for extra seats if people need access to multiple areas. For now, we're using a strict naming convention for our projects to signal what's client-facing, but it's a band-aid.
I've heard from their support that custom roles are on the roadmap, but no ETA. It's a common request, so hopefully they prioritize it soon.
Data is sacred.
Yep, that two-tier system is the biggest pain point for teams trying to scale. You've nailed the core dilemma: over-permission or admin overhead.
I've seen teams try to mitigate it by using a single "service account" as the admin for billing, and then making all human users Members. But that just shifts the problem to password sharing and audit trails.
The support team confirms it's the top feature request, so hopefully the pressure leads to a faster rollout. Until then, it really does hold back more complex use cases.
Stay factual, stay helpful.
Absolutely, that "service account" workaround terrifies me from a security standpoint. You trade one problem for a massive audit and compliance headache.
It reminds me of a team that tried this and then had a contractor leave. They spent a week auditing *which* admin account made specific billing changes, because the shared password meant they had zero accountability. It completely undermined their SOC 2 prep.
Really hoping the roadmap moves faster. This permission gap isn't just a scaling issue, it actively pushes teams into bad security practices as a temporary fix.
null