Mid-to-large retailers operating across multiple channels accumulate a silent problem over time: employees with access to systems they no longer need, passwords shared between shifts, and generic logins that no one is quite sure who is using. When someone leaves the company, how many systems were actually disconnected?
Version 32.6.1 of the Logstore platform and LogApp introduces SSO as an access protection layer for those operating at scale who need real control over who enters, what they see, and when their access is revoked.
What is SSO?
SSO stands for Single Sign-On: a unified authentication method that allows employees to access multiple systems with a single corporate login. Instead of managing different passwords for every tool, access is funneled through a single authentication point controlled by the company.
In practice: the employee logs in once with their corporate credentials and accesses only what they are authorized to see. No more forgotten passwords, no more shared generic logins, and no more open doors after a contract ends.
How SSO works on the Logstore platform
- Centralized authentication via corporate provider: access to the Logstore platform and LogApp is routed through the identity provider already used by the company, such as Google Workspace, Microsoft Azure AD, or other SAML-compliant services. The IT team configures it once and manages it from a single location.
- Role-based permission control: each employee accesses only what their job requires. The order picker sees the picking queue. The store manager sees unit metrics. The operations director sees the consolidated view. No access beyond what is necessary, with no manual configuration per system.
- Immediate deactivation upon termination: when an employee leaves the company, access is revoked in the corporate provider and automatically propagated to the Logstore platform and LogApp. No more lists of systems to remember to disconnect, and no risk of lingering access.
- Access traceability: every system entry is logged with the user, time, and device. When data inconsistencies appear, the audit has a concrete starting point.
What changes starting with version 32.6.1
SSO is available on the Logstore platform and LogApp starting with version 32.6.1, compatible with identity providers that follow the SAML 2.0 standard. Activation is performed by the IT team via the configuration panel, with no need for changes to existing infrastructure.
For teams already using Google Workspace or Microsoft Azure AD, the integration leverages existing configurations. Onboarding new employees follows the same standard corporate workflow: once an account is created in the provider, it is immediately available on the platform.
Why does this matter for operations?
Retailers operating with five systems open at once and teams working in shifts cannot manage access security manually. There are dozens of employees, multiple stores, natural industry turnover, and passwords that become "oral tradition" within the team.
SSO is not an extra layer of complexity. It is the removal of a complexity that already exists and was previously unmeasured. For the IT team, access management stops being a recurring ticket and becomes a centralized configuration. For the operations director, the risk of unauthorized access to inventory, order, and margin data is no longer a guess—it becomes auditable and controlled.
Access security is not an implementation detail
The platform that stores your business's inventory, order, and margin data must offer real control over who can access it and what they can see. This is the standard that Logstore delivers starting with version 32.6.1.
