Here’s a problem every growing operation hits eventually: your platform has a handful of broad roles, and none of them quite fit the person you’re trying to set up. You either give them more access than they should have, or you lock them out of something they actually need for their job. You pick the least-bad option and move on.
That’s been a limitation of ZenShows — until now.
Access that matches your actual org chart
You can now assign permissions capability by capability, person by person. A finance analyst doesn’t have to inherit the same access bundle as a regional lead. A coordinator gets exactly the tools their job requires, without opening doors you’d rather keep closed. It’s not a template you shoehorn people into — it’s access that reflects how your team is actually structured.
To make that practical, we’ve reorganized the permissions list by real business areas: finance, inventory, staff management, company settings, communications, and so on. Each family has consistent naming, so you’re not deciphering overlapping or vague labels trying to figure out which checkbox does what. Finance-related tools, for example, all live together now instead of being scattered across unrelated sections.
We also retired a set of obsolete duplicate entries that had built up over time. Your historical records are fully traceable — nothing is silently deleted — but the list you’re assigning from today reflects the product as it actually exists.
Regional managers who only see their region
User groups take this further for field staff. You can now define groups — by region, territory, program, team, or any combination — and scope a manager or coordinator to see and manage only the reps in those groups.
If you run events in Mexico, the person managing that program sees Mexico reps. Not your U.S. roster. Not Canada. Just the people relevant to their job. Groups can overlap and combine, so someone responsible for multiple territories gets exactly that slice — without access to everyone else.
This keeps managers focused, reduces noise, and means you’re not handing out full roster visibility as a default just because the tool didn’t offer anything more precise.
How to set it up
Open Permission Management from the main navigation, select a staff member, and walk through the grouped capabilities — finance, inventory, staff, settings, communications — turning on only what matches their role. For rep visibility, open User Groups to define your groups and add reps, then assign group scope back in Permission Management.
If your team is using any older staff-permission screens, they’ll link you through to Permission Management — that’s the single supported surface for access management going forward.
As always, reach out if you want a hand thinking through how to structure access for your particular operation.