User roles and permissions explained
Four user roles, each with different access to features, data, and settings. Roles define who can search, invite, integrate, and see billing.
CLIENT-ONLY · Concept Explainer
Why it matters
Section titled “Why it matters”Teams operate differently. A solo recruiter wears every hat. A larger team splits work: an admin manages the workspace, recruiters source and reach out, leadership reviews without sourcing. Wiggli’s roles map to that and prevent accidental access to settings people shouldn’t touch.
The four roles
Section titled “The four roles”In descending order of access.
Owner. The account creator. Full control: billing, plan, users, integrations, all features. One per workspace.
Super Admin. Just below Owner. Uses and configures every feature, manages Admins and Recruiters. Can’t manage other Super Admins or change the Owner.
Admin. Runs day-to-day recruiting and oversees Recruiters. Can search, manage the ATS. No billing, company details, or role assignment.
Recruiter. Sources and reaches out: search, projects, campaigns, ATS push. No company settings, user management, or billing.
Common misconceptions
Section titled “Common misconceptions”More admins isn’t better. Wider access means more chances of accidental changes to settings or billing. Default to Recruiter unless someone needs Admin.
Recruiters can see shared work. They see shared team projects (Strategist and Oracle). What they can’t reach is workspace settings.
Owner and Super Admin differ. Only the Owner changes billing, the plan, or transfers ownership.
Roles are independent of plan. Upgrading doesn’t reassign permissions.
Related articles
Section titled “Related articles”Still stuck?
Your customer success manager reads faster than any search bar.