Clover User Management Guide

• Model type: hybrid
• Description: Clover uses three named role labels (Owner, Manager, Employee) as starting templates, but each employee's actual access is controlled by a set of individual permission toggles that the Owner can enable or disable per person. There are no fully custom-named roles; the role label is cosmetic beyond the Owner tier.
• Custom roles: No
• Custom roles plan: Not documented
• Granularity: Per-employee permission toggles covering areas such as: process refunds, apply discounts, edit orders, access reports, manage employees, manage inventory, access cash drawer, and more. Granularity is moderate-function-level rather than object-level.

1. Log in to the Clover web dashboard at clover.com/dashboard.
2. Navigate to Employees in the left sidebar.
3. Click 'Add Employee'.
4. Enter the employee's first name, last name, nickname (optional), email address, and phone number (optional).
5. Select a role label: Manager or Employee.
6. Set a 4-digit PIN for device login.
7. Toggle individual permissions on or off as needed.
8. Click 'Save'. The employee receives an email invitation to create a Clover account if an email was provided.

Required fields: First name, Last name, 4-digit PIN

Watch out for:

• Email address is optional but required if the employee needs web dashboard access; without it they can only log in via device PIN.
• PINs must be unique across all employees on the same merchant account.
• Employees added on one Clover device sync to all devices on the same merchant account automatically.
• If the merchant account has multiple locations, employees must be added separately per location unless using a multi-location management setup.

• Can delete users: Yes
• Delete/deactivate behavior: Clover allows permanent deletion of employee records from the dashboard. There is no native 'deactivate/suspend' toggle that preserves the record while blocking access; the primary supported action is deletion. Deleting an employee immediately revokes their PIN and any web dashboard access.

1. Log in to the Clover web dashboard at clover.com/dashboard.
2. Navigate to Employees in the left sidebar.
3. Click on the employee's name to open their record.
4. Click 'Delete Employee' (or the trash icon).
5. Confirm the deletion in the prompt.

Watch out for:

• Deletion is permanent; there is no archive or restore function for deleted employee records.
• The Owner account cannot be deleted from within the dashboard; account closure requires contacting Clover support.
• If an employee has an active shift (clocked in), deleting them may cause reporting inconsistencies; best practice is to ensure they are clocked out first.
• Deleted employees lose web dashboard access immediately but any active device sessions may persist until the device syncs or the session expires.

• Where to check usage: Clover web dashboard → Account & Setup → Billing (shows active plan and registered devices; employee count is not displayed as a billable metric).
• How to identify unused seats: No built-in 'last login' report for employees in the standard dashboard. Owners can review employee shift/clock-in history under Reports → Shifts to identify inactive employees.
• Billing notes: Clover bills per device/register, not per employee seat. Adding or removing employees has no direct impact on the monthly software subscription cost. Hardware costs and processing fees are separate. Plans require a 36-month commitment in most cases; early termination fees apply.

Clover bills per device/register, not per employee seat, so adding or removing employees has no direct impact on your monthly software cost. That removes license-recovery as a motivation for timely offboarding, which means inactive employee records tend to accumulate.

The only way to identify dormant accounts is to manually cross-reference Reports → Shifts → clock-in history - there is no built-in last-login report in the standard dashboard.

The most consistent friction reported by Clover admins centers on three gaps. First, there is no bulk employee import - every record must be created one at a time through the dashboard or a device.

Second, there is no deactivate or suspend state; the only supported action is permanent deletion, which creates problems for seasonal or temporary staff. Third, there is no audit log showing which admin changed employee records or permissions, making compliance reviews difficult.

Common complaints:

• No enterprise identity features such as SSO, SCIM provisioning, or IdP integration.
• No bulk employee import via CSV; employees must be added one at a time through the dashboard or device.
• No native 'deactivate' or 'suspend' state for employees-only permanent deletion, which some users find high-impact for seasonal or temporary staff.
• Employee permissions must be configured individually per person with no ability to save custom role templates for reuse.
• Multi-location businesses must manage employees separately per location with no centralized cross-location employee management in standard plans.
• No audit log or activity log showing which admin made changes to employee records or permissions.
• 4-digit PIN login on devices is considered a weak authentication method by some operators, with no option to enforce stronger authentication on the POS hardware.

Clover's permission model uses three named role labels - Owner, Manager, and Employee - as starting templates, but actual access is controlled by per-employee permission toggles set individually by the Owner. There are no saveable custom role templates, so every new hire requires manual toggle configuration from scratch.

Multi-location businesses face an additional burden: employees must be added separately per location with no centralized cross-location management in standard plans.

Bottom line

Clover is purpose-built for SMB point-of-sale operations, and its employee management reflects that scope. Every app in a modern SaaS stack typically offers at least a deactivation state and some form of audit logging - Clover offers neither.

For small, stable teams with a single location, the manual dashboard workflow is manageable. For businesses with high staff turnover, multiple locations, or any identity governance requirement, the absence of SCIM, SSO, bulk import, and audit logs creates meaningful operational overhead that compounds with headcount.