Rippling User Management Guide

• Model type: hybrid
• Description: Rippling uses a hybrid model combining predefined built-in roles (Super Admin, standard employee) with fully customizable role-based permission sets. Admins can create custom roles scoped by module, employee group (e.g., by department, location, employment type), and action type (view, edit, approve, manage). Permissions are enforced per Rippling module (HR Cloud, IT Cloud, Finance Cloud) independently.
• Custom roles: Yes
• Custom roles plan: Available on standard Rippling subscriptions; specific granularity tied to purchased modules
• Granularity: Module-level, employee-group-level, and action-level (view/edit/approve). Admins can restrict a role to manage only employees in a specific department or location.

1. Log in to Rippling at app.rippling.com as an admin with employee management permissions.
2. Navigate to HR Cloud → Employees (or the main People section).
3. Click 'Add Employee' or 'Start Onboarding'.
4. Enter required worker information: legal name, work email, start date, employment type (employee or contractor), department, and work location.
5. Select the employee's compensation details and job information.
6. Choose which apps and devices to provision (if IT Cloud is active).
7. Assign any applicable benefits, payroll, and compliance tasks.
8. Send the onboarding invitation; the new user receives an email to complete their profile and set up their account.

Required fields: Legal first and last name, Work email address, Start date, Employment type (employee or contractor), Department, Work location, Compensation type and amount, FLSA classification (exempt/non-exempt for US employees)

Watch out for:

• Adding a user triggers the full onboarding workflow including payroll, benefits, and IT provisioning steps - admins must complete or skip each section before the record is saved.
• Work email must be unique; Rippling does not allow duplicate email addresses across active or terminated worker records.
• If IT Cloud is active, app provisioning rules may automatically assign software licenses upon hire, which can affect billing immediately.
• Rippling requires a minimum of 5 employees on the account.
• International employees may require additional country-specific modules (Rippling Global) which are separately priced.

• Can delete users: No
• Delete/deactivate behavior: Rippling does not permanently delete employee records. Removing a user is handled through the 'Terminate Employee' workflow, which deactivates the worker record and triggers offboarding tasks. The record is retained in a terminated/inactive state for compliance, payroll history, and reporting purposes. Terminated records can be viewed under the 'Terminated' filter in the Employees list.

1. Log in to Rippling at app.rippling.com as an admin with termination permissions.
2. Navigate to HR Cloud → Employees and locate the employee record.
3. Open the employee profile and click 'Terminate Employee' (or use the action menu).
4. Enter the termination date, termination reason, and whether the departure is voluntary or involuntary.
5. Review and complete offboarding tasks: final paycheck processing, benefits termination, equipment retrieval, and app deprovisioning.
6. Confirm the termination. Rippling will automatically trigger configured offboarding workflows including revoking access to provisioned apps (if IT Cloud is active).

Watch out for:

• Termination date determines when access is revoked; setting a future termination date means the employee retains access until that date.
• Final paycheck processing must be handled within Rippling Payroll before or at termination; state-specific final pay laws are not automatically enforced - admins must configure compliance settings.
• If the employee has outstanding expense reports or approvals, these must be resolved before or after termination as the workflow does not automatically block termination.
• Rehiring a terminated employee reactivates their existing record rather than creating a new one, preserving historical data.
• Benefits termination (e.g., health insurance) follows the plan's termination rules (end of month vs. last day of employment) and must be verified against carrier requirements.

• Where to check usage: IT Cloud → App Management → [Select App] → view assigned users and license count; HR Cloud → Employees → filter by Active to see billable headcount
• How to identify unused seats: IT Cloud → App Management allows admins to view per-app user assignments and identify employees assigned to an app who have not logged in within a configurable period. Rippling does not have a native 'unused license' dashboard across all apps; identification requires reviewing each connected app individually.
• Billing notes: Rippling uses modular pricing - each HR, IT, and Finance Cloud product is billed separately per employee per month. The base Unity platform fee (~$8/user/mo) applies to all seats plus a $35/mo base fee. Adding or removing employees mid-cycle affects billing on a prorated basis. Some products (e.g., ATS) have reported base fees of $4,000+ annually regardless of headcount. A minimum of 5 employees is required. All pricing is quote-based and not publicly listed; figures cited are based on reported ranges.

Rippling's modular structure means total cost scales with the products you enable. HR Cloud bundles are reported at $15–$29/employee/mo depending on modules selected; IT Cloud and Finance Cloud are separately quoted.

Some products, such as the ATS, carry reported base fees of $4,000+ annually regardless of headcount. A minimum of 5 employees is required across the account. Because pricing is not publicly listed, teams frequently report difficulty forecasting total cost as modules are added over time.

Community evidence is not specific enough to quote or summarize yet for this app.

Rippling is a strong fit for teams that want a single platform to manage HR, IT, and Finance workflows and are willing to invest in configuration upfront. The hybrid permission model - combining Super Admin, custom role-based access, and module-level scoping - gives precise control over every app and every employee group.

Teams with simpler needs or tighter budgets should weigh the modular cost structure carefully, particularly if international payroll (Rippling Global) is required, as that is a separate, higher-cost module not included in standard HR Cloud pricing.

Bottom line

Rippling centralizes the full employee lifecycle - from onboarding to offboarding - and pushes provisioning to every app through its IT Cloud layer. The platform rewards teams that invest in configuration: automated workflows, granular role scoping, and app provisioning rules reduce ongoing manual work significantly.

The tradeoffs are real - modular pricing escalates with adoption, support response times are reported as slow outside enterprise tiers, and any app not connected via IT Cloud falls outside Rippling's automated offboarding coverage.