Admin vs User Roles and Permissions in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

Sparkforge has agency-level and sub-account-level roles. Agency Admins manage everything globally; Sub-Account Admins have full access inside their assigned account. Permissions stack across levels and broader scopes always win.

Sparkforge separates roles into two scopes: agency-level (global) and sub-account-level (one client). Each scope has Admin and User roles. Use this matrix to decide which scope and role to assign.

Permission matrix

Agency-only permissions

Create, edit, and delete sub-accounts.
Manage SaaS Mode and reselling.
Global integrations (Mailgun, Twilio rebilling, Google API, etc.).
Snapshot management.
Agency-level billing and branding.
Agency settings (company info, rebilling).
White-label settings (custom domains, logos, colors).

Sub-account-only permissions

Pipelines and opportunities.
Workflows and campaigns.
Calendars and appointment settings.
Conversations (SMS, email, chat).
Contact management and Smart Lists.
Reputation management.
Funnel and website builder.

Available at both levels

User management — admins add and edit users at their own level.
Dashboard reporting.
Media library.
Audit logs.

If a permission isn't listed, assume it inherits the broader role's default at its level.

Change a user's role

Go to Settings > My Staff.
Click the pencil icon to edit the user.
Scroll to User Roles and expand it.
Adjust the role and save.

How permissions stack

If a user holds an Agency-level role and Sub-Account-level access, the two scopes stack — they don't cancel each other out. The broader Agency permission always takes precedence inside the sub-accounts the user can reach.

Frequently Asked Questions

Can an Agency Admin restrict a Sub-Account Admin's permissions?

No. Sub-Account Admins always have full access inside their assigned sub-account. To limit scope, assign a User role instead of an Admin role at the sub-account level.

If a permission exists at both levels, who wins?

Agency Admins. Their actions apply across every sub-account; Sub-Account Admin actions are scoped to their own account.

What happens if a user has both an Agency role and a Sub-Account role?

Both scopes apply at the same time. Permissions stack — Agency permissions take precedence wherever they overlap with Sub-Account permissions.

Do all Agency Admins get Login As?

Not automatically. Login As is gated by the Enable Login As permission. If it's disabled for an admin, the option is hidden from their UI.

How do I prevent a sub-account staffer from editing automations?

Assign them a User role (not Admin) at the sub-account level, then turn off the relevant permission. Sub-Account Users can be scoped per-feature; Sub-Account Admins cannot.