Stitchflow
LinkedIn Recruiter logo

LinkedIn Recruiter User Management Guide

Manual workflow

How to add, remove, and manage users with operational caveats that matter in production.

UpdatedMar 11, 2026

Summary and recommendation

LinkedIn Recruiter user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.

LinkedIn Recruiter seat management is entirely manual - there is no SCIM, no automated provisioning, and no API surface for user lifecycle operations. Every app in your stack that connects to an IdP for automated onboarding and offboarding will hit a hard wall here.

Contract Admins handle all seat assignments through the LinkedIn Recruiter admin console at linkedin.com/talent/recruiter/settings.

Two distinct products exist under the Recruiter umbrella: Recruiter Lite and Recruiter Corporate. Lite accounts have no centralized admin console and are managed per-seat through individual LinkedIn account settings. Corporate contracts have a shared admin panel, pooled InMail credits, and support for SSO - but SSO covers authentication only, not provisioning.

Quick facts

Admin console pathLinkedIn Recruiter > Admin Settings (top navigation, gear icon) > Manage Seats / User Management
Admin console URLOfficial docs
SCIM availableNo
SCIM tier requiredEnterprise
SSO prerequisiteNo

User types and roles

Role Permissions Cannot do Plan required Seat cost Watch out for
Contract Admin Full administrative control over the Recruiter contract: add/remove seats, assign roles, manage billing contacts, view usage reports, configure SSO settings, access all projects and InMail activity across the contract. Cannot exceed the contracted seat count without a contract amendment; cannot self-serve increase InMail allotments beyond purchased amount. LinkedIn Recruiter Corporate (multi-seat contract) Consumes one licensed seat Only users designated as Contract Admin can add or remove other users. There can be multiple Contract Admins on a single contract, but at least one must remain at all times.
Recruiter (Standard Seat) Access to full LinkedIn Recruiter search, InMail sending (up to contracted monthly allotment), project creation and management, candidate pipeline management, collaboration on shared projects, notes and tags on candidate profiles. Cannot manage seats, cannot view contract billing details, cannot assign or revoke roles for other users, cannot access admin settings. LinkedIn Recruiter Corporate (multi-seat contract) One licensed seat per user InMail credits are pooled at the contract level on Corporate plans; individual users draw from the shared pool. On Lite, InMails are per-seat and do not pool.
Hiring Manager (Recruiter Lite or Corporate add-on) Can view candidate profiles shared by recruiters, leave feedback/notes on candidates within shared projects, limited search capability depending on plan. Cannot send InMails independently (on some configurations), cannot manage contract settings, cannot create new projects without recruiter involvement. LinkedIn Recruiter Corporate (Hiring Manager access is a feature of multi-seat Corporate contracts; not available on Lite) Consumes one licensed seat Hiring Manager seat availability and exact permissions vary by contract configuration; confirm with LinkedIn account representative.
Recruiter Lite User Individual recruiter search, 30 InMails/month (per seat, non-pooled), basic candidate tracking, limited project collaboration. Cannot pool InMails with other users, no team collaboration features, no shared projects across seats, no Hiring Manager access, no advanced analytics. LinkedIn Recruiter Lite (single-seat or small team, self-serve subscription) Approximately $170/month per seat (self-serve pricing; subject to change) Recruiter Lite is a separate product from Recruiter Corporate. Lite accounts managed individually via LinkedIn account settings, not a centralized admin console. Upgrading from Lite to Corporate requires a new contract.

Permission model

  • Model type: role-based
  • Description: LinkedIn Recruiter uses a fixed role-based permission model with two primary roles: Contract Admin and Recruiter (seat user). Hiring Manager is an additional role available on Corporate contracts. There are no custom roles or granular permission sets. Admins assign roles at the seat level when provisioning users.
  • Custom roles: No
  • Custom roles plan: Not documented
  • Granularity: Coarse - permissions are bundled by role. No ability to grant or restrict individual feature access within a role. All standard Recruiter seats have identical permissions.

How to add users

  1. Log in to LinkedIn Recruiter with a Contract Admin account.
  2. Click the Admin Settings icon (gear icon) in the top navigation bar.
  3. Select 'Manage Seats' or 'User Management' from the admin menu.
  4. Click 'Add Seat' or 'Invite User'.
  5. Enter the LinkedIn member's email address or name to locate their LinkedIn profile.
  6. Select the role to assign (Recruiter or Contract Admin).
  7. Click 'Send Invitation' or 'Add User'. The invited user receives an email notification and must accept to activate their seat.
  8. Confirm the seat appears as active in the seat management dashboard.

Required fields: LinkedIn member email address or full name (to locate their LinkedIn profile), Role assignment (Recruiter or Contract Admin)

Watch out for:

  • The invited user must have an existing LinkedIn personal account. LinkedIn Recruiter seats are tied to individual LinkedIn member profiles, not just email addresses.
  • Adding a seat beyond the contracted number requires contacting LinkedIn Sales to amend the contract; self-serve seat expansion is not available.
  • Invitation must be accepted by the user before the seat is active and consuming the license.
  • On Recruiter Lite, seat management is handled through individual LinkedIn account settings, not a centralized admin console.
  • SSO configuration (if applicable) must be completed before users can authenticate via SSO; this is a separate admin step.
Bulk option Availability Notes
CSV import No Not documented
Domain whitelisting No Automatic domain-based user add
IdP provisioning No Not documented

How to remove or deactivate users

  • Can delete users: No
  • Delete/deactivate behavior: LinkedIn Recruiter does not delete user accounts. Removing a user deactivates their access to the Recruiter contract (revokes the seat), but their underlying LinkedIn personal profile is unaffected. The seat is freed and can be reassigned to another user. Historical activity (InMails sent, notes, project contributions) associated with the removed user remains in the contract's records.
  1. Log in to LinkedIn Recruiter with a Contract Admin account.
  2. Navigate to Admin Settings (gear icon) > Manage Seats / User Management.
  3. Locate the user to be removed in the seat list.
  4. Click the options menu (three dots or 'Edit') next to the user's name.
  5. Select 'Remove Seat' or 'Revoke Access'.
  6. Confirm the removal when prompted.
  7. The seat is immediately freed and the user loses access to the Recruiter contract.
Data impact Behavior
Owned records Projects, candidate notes, and tags created by the removed user remain in the contract and are accessible to remaining Contract Admins and seat holders. Data is not deleted.
Shared content Shared projects and pipeline data the removed user contributed to remain intact and accessible to other team members on the contract.
Integrations Any ATS integrations configured at the contract level are unaffected. If the removed user had personal integration tokens or ATS-linked workflows, those connections may need to be reconfigured by an active user.
License freed The seat is freed immediately upon removal and can be reassigned to a new user without waiting for a billing cycle. The contract's total seat count and billing remain unchanged until the contract is amended.

Watch out for:

  • Removing a user does not reduce the contracted seat count or billing. The seat remains billable until the contract is renegotiated or the renewal date.
  • The removed user retains their personal LinkedIn account and any InMail credits that were part of a Lite individual subscription.
  • On Corporate contracts with pooled InMails, unused InMail credits from the removed user's activity remain in the shared pool.
  • There is no grace period or 'suspended' state - removal is immediate and the user loses access instantly.
  • Contract Admins cannot remove themselves if they are the sole Contract Admin; another admin must be designated first.

License and seat management

Seat type Includes Cost
Recruiter Lite Seat 30 InMails/month (non-pooled, per seat), basic candidate search and tracking, limited project features, individual account management. Approximately $170/month per seat (self-serve; ~$1,440–$2,700/year depending on billing cycle and promotions)
Recruiter Corporate Seat 150+ InMails/month (pooled across contract), advanced search filters, team collaboration, shared projects, Hiring Manager access, analytics dashboard, ATS integrations, SSO support. Approximately $750–$900/month per seat (~$8,999–$10,800/year); multi-seat contracts from ~$12,000+/year; custom pricing based on company size and negotiation
  • Where to check usage: Admin Settings (gear icon) > Usage Reporting or Analytics > Seat Activity / InMail Usage dashboard within LinkedIn Recruiter
  • How to identify unused seats: Contract Admins can view last login date and InMail activity per seat in the Admin Settings > Manage Seats view. Seats with no recent login or zero InMail usage over a rolling period can be identified for reallocation.
  • Billing notes: LinkedIn Recruiter Corporate is sold as an annual contract with fixed seat counts. Adding seats mid-contract is prorated; removing seats does not reduce billing until contract renewal. InMail credits on Corporate plans are pooled monthly and do not roll over to the next month. Additional InMails can be purchased at approximately $10 each. Recruiter Lite is billed monthly or annually via self-serve LinkedIn subscription; cancellation stops future billing but access continues through the paid period.

The cost of manual management

Seat billing on Corporate contracts is annual and fixed. Adding a seat mid-contract is prorated; removing a seat does not reduce billing until the next renewal. Teams that downsize mid-year continue paying for unused seats with no self-serve relief path.

InMail credits on Corporate plans pool monthly across the contract and do not roll over. Unused credits at the end of a billing period are forfeited. Additional InMails can be purchased individually, and job slots carry their own per-slot costs on top of seat fees.

There is no bulk import or CSV upload for provisioning. Each user must be invited individually by email or LinkedIn profile name, and the invitation must be accepted before the seat activates. This makes every hire and every departure a manual, one-at-a-time operation.

What IT admins are saying

The most consistent complaint from admins is the inability to reduce seat count mid-contract. Teams that lose recruiters mid-year are locked into paying for idle seats until renewal, and removing a user does not trigger any billing adjustment or notification to finance.

Admins also flag the absence of bulk provisioning. No CSV upload, no directory sync, no automated deprovisioning - every change is a manual UI action.

The split experience between Lite (no admin console) and Corporate (centralized console) adds confusion for organizations managing both product tiers.

InMail credit expiration at month-end is a recurring frustration on Corporate plans. Credits that go unused - often because a seat was vacated mid-month - are lost with no rollover mechanism.

Common complaints:

  • Admins cannot reduce seat count mid-contract; billing continues for unused seats until annual renewal, which is a common source of frustration for teams that downsize.
  • No bulk user import or CSV upload for provisioning multiple seats at once; each user must be invited individually.
  • No SCIM or automated provisioning support, requiring manual seat management for every hire and departure.
  • Removing a user does not automatically notify the billing team or reduce invoice amounts, leading to unexpected charges.
  • Users report confusion between Recruiter Lite and Recruiter Corporate admin experiences, as Lite has no centralized admin console.
  • InMail credits do not roll over month-to-month on Corporate plans, leading to perceived waste at end of billing period.
  • SSO is available but SCIM is not supported, meaning offboarding requires manual seat removal even when the IdP account is deprovisioned.
  • Contract Admins report difficulty identifying inactive seats because usage reporting is not prominently surfaced in the admin UI.
  • Pricing is opaque and requires sales engagement for Corporate contracts; self-serve pricing for Lite changes without clear notice.

The decision

LinkedIn Recruiter is appropriate for organizations that can absorb fully manual seat lifecycle management and are prepared to treat provisioning and deprovisioning as recurring IT tasks with no automation path. SSO via SAML 2.0 is available on Corporate contracts and handles authentication, but it does not extend to seat assignment or removal.

Organizations with high recruiter turnover or frequent headcount changes will feel the operational weight most acutely. Every departure requires a manual admin action, and billing does not self-correct. Teams should build offboarding checklists that explicitly include LinkedIn Recruiter seat removal as a discrete step.

Recruiter Lite is a separate product with a separate management experience. If your organization uses both tiers, expect two distinct admin workflows with no unified view.

Bottom line

LinkedIn Recruiter has no SCIM, no user management API, and no automated provisioning path of any kind. Every app in your environment that relies on directory-driven lifecycle management will require a manual workaround here.

Seat operations - adding, reassigning, and removing users - are Contract Admin tasks performed one at a time in the LinkedIn Recruiter admin console. Billing does not adjust when seats go idle mid-contract, so offboarding discipline directly affects spend.

SSO is available on Corporate contracts for authentication but does not substitute for provisioning. Teams should treat LinkedIn Recruiter as a fully manual system and plan operational capacity accordingly.

Automate LinkedIn Recruiter workflows without one-off scripts

Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.

Every app coverage, including apps without APIs
60+ app integrations plus browser automation for apps without APIs
IT graph reconciliation across apps and your IdP
Less than a week to launch, maintained as APIs and admin consoles change
SOC 2 Type II. ~2 hours of your team's time

UpdatedMar 11, 2026

* Details sourced from official product documentation and admin references.

Keep exploring

Related apps

6sense logo

6sense

Manual Only
AutomationNot Supported
Last updatedFeb 2026

6sense user management lives entirely in Settings > User Management (https://analytics.6sense.com/settings/user-management). The platform uses a role-based access control model scoped per product module — ABM, Sales Intelligence (SI), and Conversationa

Alkami logo

Alkami

Manual Only
AutomationNot Supported
Last updatedMar 2026

Alkami is an enterprise-only digital banking platform sold exclusively to financial institutions such as banks and credit unions. It is not a general-purpose SaaS tool, and its admin and user-management documentation is not publicly available. Independ

AmazingHiring logo

AmazingHiring

Manual Only
AutomationNot Supported
Last updatedMar 2026

AmazingHiring is a recruiter-facing sourcing platform sold on a pay-per-seat, annual billing model. There is no native SCIM support and no publicly documented IdP integration, which means every app lifecycle event — onboarding, role change, offboarding