Stitchflow
Lightspeed logo

Lightspeed 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

Lightspeed 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.

Lightspeed manages employees across two separate Back Office portals: Retail (retail.lightspeedhq.com) and Restaurant (restaurant.lightspeedhq.com). Employee records are not shared across product lines, so teams running both Retail and Restaurant must manage staff in each system independently. The primary navigation path is Back Office > Employees (Retail) or Back Office > Staff (Restaurant).

Lightspeed uses three baseline roles - Owner, Manager, and Employee - with a hybrid permission model that allows per-employee permission toggles on higher-tier plans. Custom permission sets are locked behind Advanced or X-Series plans; Basic and Core plans are limited to fixed role templates with no granular overrides.

Quick facts

Admin console pathLightspeed Retail: Back Office > Employees; Lightspeed Restaurant: Back Office > Staff
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
Owner / Account Owner Full access to all Back Office settings, billing, employee management, reports, and POS configuration. Cannot be removed or demoted by other users. Cannot transfer ownership without contacting Lightspeed support. All plans (one per account) Included in base plan Only one Owner role exists per account. Ownership transfer requires a support ticket.
Manager Access to most Back Office functions including reports, inventory, and employee management. Can apply discounts and process refunds at POS. Cannot access billing settings or change account ownership. Specific Back Office sections can be restricted by Owner. All plans Included; no additional per-seat charge documented for standard plans Manager permissions can be customized per employee via custom permission sets on higher-tier plans.
Employee / Cashier POS-only access by default: process sales, apply pre-approved discounts, manage their own clock-in/out. Cannot access Back Office, view reports, manage inventory, or change settings unless specific permissions are granted. All plans Included; no additional per-seat charge documented for standard plans Default Employee role is highly restricted. Granular permissions must be manually enabled per employee.
Custom Role (Retail X-Series / Advanced plans) Fully configurable permission set applied per employee. Permissions span POS actions, Back Office sections, and reporting. Lightspeed Retail Advanced or X-Series (exact plan name varies by region; contact Lightspeed for confirmation) Custom roles are not available on Basic/Core plans. Upgrading plan is required to unlock granular custom permissions.

Permission model

  • Model type: hybrid
  • Description: Lightspeed uses predefined roles (Owner, Manager, Employee) as a baseline, with the ability to create custom permission sets per employee on higher-tier plans. Permissions cover POS actions (discounts, refunds, voids, drawer access) and Back Office sections (reports, inventory, employee management, billing). Each permission is toggled individually per employee profile.
  • Custom roles: Yes
  • Custom roles plan: Lightspeed Retail Advanced or X-Series (plan name varies by region; not available on Basic or Core)
  • Granularity: Per-employee permission toggles across POS actions and Back Office sections. Includes controls for: apply discounts, process refunds, void transactions, access reports, manage inventory, manage employees, access cash drawer, and more.

How to add users

  1. Log in to Lightspeed Back Office with Owner or Manager credentials.
  2. Navigate to Employees (Retail) or Staff (Restaurant) in the left-hand menu.
  3. Click 'Add Employee' or 'New Staff Member'.
  4. Enter required fields: first name, last name, email address, and PIN (for POS login).
  5. Assign a role (Owner, Manager, Employee) or select a custom permission set if available on your plan.
  6. Configure individual permission toggles as needed.
  7. Save the employee record. An invitation email is sent to the provided email address for Back Office access.

Required fields: First name, Last name, Email address (for Back Office login), PIN (for POS terminal login)

Watch out for:

  • POS login uses a numeric PIN, not the email/password used for Back Office. These are separate credentials.
  • Employees without Back Office access still require an email address on file.
  • New employees receive an email invitation to set their Back Office password; if the email is not received, check spam or resend from the employee record.
  • Custom permission sets are only available on Advanced/X-Series plans; Basic and Core plans use fixed role templates.
  • Lightspeed has multiple product lines (Retail, Restaurant, eCom); employee management interfaces differ between products and accounts are not shared across product lines.
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: Lightspeed does not permanently delete employee records. Employees can be deactivated (archived), which removes their ability to log in to the POS or Back Office while retaining their historical transaction and sales data for reporting purposes.
  1. Log in to Back Office with Owner or Manager credentials.
  2. Navigate to Employees (Retail) or Staff (Restaurant).
  3. Locate the employee record to deactivate.
  4. Open the employee profile and toggle the employee status to 'Inactive' or click 'Archive' (label varies by product version).
  5. Save changes. The employee's PIN and Back Office login are immediately disabled.
Data impact Behavior
Owned records Historical sales transactions, clock-in/out records, and reports attributed to the employee are retained and remain accessible to Owners and Managers.
Shared content Inventory changes, customer records, and other data created by the employee remain in the system and are not removed.
Integrations No documented automatic impact on third-party integrations upon deactivation; integrations referencing employee IDs may need manual review.
License freed Lightspeed plans are not documented as per-seat licensed for standard employee accounts; deactivating an employee does not reduce a seat count or billing amount on standard plans.

Watch out for:

  • Deactivated employees cannot be permanently deleted; their records remain in the system.
  • If an employee is also an account Owner, ownership must be transferred via Lightspeed support before deactivation.
  • Deactivated employees still appear in historical reports attributed to their name.
  • Reactivating a previously deactivated employee restores their profile and historical data.

License and seat management

Seat type Includes Cost
Base Plan License (Retail) Unlimited employee profiles on most plans; POS register count is the primary licensing unit, not per-user seats. Basic $89/mo, Core $149/mo (USD, billed annually; pricing subject to change)
Base Plan License (Restaurant) Staff profiles included; licensing based on number of terminals/registers, not per-user seats. Varies by plan; contact Lightspeed for current pricing
  • Where to check usage: Back Office > Employees (Retail) or Back Office > Staff (Restaurant) to view all active and inactive employee records.
  • How to identify unused seats: Filter employee list by 'Active' status and cross-reference last login date or last transaction date in reports. No automated unused-seat detection tool is documented.
  • Billing notes: Lightspeed's primary billing unit is the number of POS registers/terminals, not the number of employee user accounts. Adding employees does not directly increase the monthly bill on standard plans. Enterprise and multi-location pricing is custom and requires contacting Lightspeed sales.

The cost of manual management

Every app in a Lightspeed environment requires manual employee entry one record at a time - there is no bulk import tool documented for any product line. Each new hire requires first name, last name, email, and a numeric POS PIN, with Back Office access and POS access using entirely separate credentials.

Admins must track both systems independently.

Ownership transfers cannot be completed self-serve; they require opening a support ticket with Lightspeed, which community reports flag as slow to resolve. Deactivated employees cannot be permanently deleted, so employee lists accumulate archived records over time with no automated cleanup path.

What IT admins are saying

Recurring friction points reported by Lightspeed users center on three areas. First, the permission system on Basic and Core plans is widely described as too rigid, with no path to custom roles without a plan upgrade.

Second, the dual-credential system - POS PIN versus Back Office email/password - causes consistent confusion during staff onboarding.

Third, account ownership changes require a support ticket rather than a self-serve transfer, and users report slow response times in that process. Deactivated employee records persisting indefinitely in the employee list is also a frequently cited annoyance, particularly for high-turnover retail environments.

Common complaints:

  • Users report that the permission system on Basic and Core plans is too rigid, with no ability to create custom roles without upgrading to a higher-tier plan.
  • Multiple users note that there is no bulk import option for employees, requiring manual entry of each staff member one at a time.
  • Users report confusion between POS PIN login and Back Office email/password login, particularly when onboarding new staff.
  • Some users report difficulty transferring account ownership, as it requires contacting Lightspeed support rather than being self-serve.
  • Users on community forums note that deactivated employees cannot be permanently deleted, which creates clutter in employee lists over time.
  • Reports of slow or unresponsive Lightspeed support when requesting account ownership changes or resolving locked-out admin accounts.
  • Users managing multiple locations note that employee profiles are not shared across locations by default and must be recreated per location in some configurations.

The decision

Lightspeed's permission model is adequate for small retail or restaurant teams where Owner and Manager roles cover most access needs. For organizations that need granular, role-based access control across every app and every employee, the Advanced or X-Series plan is a prerequisite - Basic and Core plans will not support it.

Teams managing both Retail and Restaurant product lines should account for the operational overhead of maintaining two separate employee directories with no cross-product sync. If ownership of the account is ever in question, plan for support ticket lead time rather than an instant self-serve resolution.

Bottom line

Lightspeed's employee management works reliably for straightforward retail and restaurant staffing, but it carries meaningful manual overhead: no bulk import, no self-serve ownership transfer, no permanent deletion, and a dual-credential system that requires clear onboarding documentation for every app and every new hire.

Teams that need granular permissions must be on Advanced or X-Series plans, and those running multiple Lightspeed product lines will manage entirely separate employee directories with no shared identity layer between them.

Automate Lightspeed 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

Abnormal Security logo

Abnormal Security

API Only
AutomationAPI only
Last updatedMar 2026

Abnormal Security is an enterprise email security platform focused on detecting and investigating threats such as phishing, account takeover (ATO), and vendor email compromise. It does not support SCIM provisioning, which means every app in your stack

ActiveCampaign logo

ActiveCampaign

API Only
AutomationAPI only
Last updatedFeb 2026

ActiveCampaign uses a group-based permission model: every user belongs to exactly one group, and all feature-area access (Contacts, Campaigns, Automations, Deals, Reports, Templates) is configured at the group level, not per individual. The default Adm

ADP logo

ADP

API Only
AutomationAPI only
Last updatedFeb 2026

ADP Workforce Now is a mid-market to enterprise HCM platform that serves as the HR source of record for employee data — payroll, benefits, time, and talent. User access is governed by a hybrid permission model: predefined security roles (Security Maste