As a business grows past a handful of active accounts, one admin approving every campaign, schedule change, and contact import becomes a bottleneck — but handing out full admin access to every team lead trades a bottleneck for a bigger risk.
The middle ground: scoped delegation
GrapMe's Sub-Admin role sits between User and Super Admin. A sub-admin can be assigned a specific set of users or campaigns, and granted specific capabilities against just that scope — for example, "approve campaigns and schedules for these three accounts," without visibility into anything else on the tenant.
What a sub-admin can and can't see
- Can: review and approve/reject items in their assigned queue, view reports for their assigned users, manage credits if that permission is granted.
- Can't: touch global settings or billing, create other sub-admins, or see users/campaigns outside their assignment — that stays reserved for Super Admin.
Why this matters for reporting, too
Scoping isn't just about who can click "approve." Dashboard aggregates follow the same rule: a sub-admin's view of active campaigns, bounce rate, and open/click rate is automatically filtered to their assigned scope, so reporting doesn't require manually filtering out accounts that aren't theirs.
A concrete example
A fast-growing business with 40 active accounts might run three team leads as sub-admins, each responsible for roughly a third of them. Each approves their own team's campaigns and sees only their own team's dashboard — while the super admin retains a single, unfiltered view across all 40 accounts and can step in on any queue at any time.
That's the model: delegate the day-to-day approval work, keep the full picture at the top. Talk to us about how assignment would map onto your team structure.