Skip to content

Security

Permission first, scope always, a trail on every action.

In PERSO every screen and every action opens with a permission; data is bounded by company, branch and site scope; critical actions are written to the audit trail. This page summarises the security model implemented in the product, in product language.

  1. 01

    Role and permission management

    Roles are built from permission sets; each product has separate view and act permissions. Screen visibility depends on the licence, actions on permissions.

  2. 02

    Permission-first authorisation

    Actions that require a permission are checked permission-first; on top of that, module/licence, tenant and scope or data-driven checks apply together.

  3. 03

    Scope

    Company, branch, site and “only my own records” scopes draw different data boundaries within the same role.

  4. 04

    Tenant isolation

    Each company’s data stays within its own scope; cross-company access is blocked on the server.

  5. 05

    Audit trail

    Critical create, update, approval and correction actions are recorded with who and when.

  6. 06

    Public and token surfaces

    External surfaces such as the supplier portal, QR and asset tags work with time-limited, signed access.

  7. 07

    Role separation

    Platform administration and company administration are separate roles with separate scopes.

  8. 08

    Account and data safety

    Secure password reset, sensitive-field masking, account deletion requests and infrastructure that supports privacy processes.

Why One Platform?

Nine platform products, one shared backbone.

PERSO products are scoped to your business needs; the products, capabilities and commercial package structure are settled during the quote process. The nine platform products work together on the same PERSO One Platform; WMS, IoT, Vision and Smart Expense are separate ecosystem products included in scope on request.

  • One user experience

    One sign-in, a product launcher and switching between products; every product speaks the same interface language.

  • Company / branch structure

    The multi-company and multi-branch model is the shared scope of all products.

  • Users and roles

    Users, roles and permissions are defined on the platform; products inherit them.

  • Tenant isolation

    Each company’s data stays within its own scope; access is checked at company and branch boundaries.

  • Notifications and tasks

    Approvals, tasks and notifications flow through a shared infrastructure.

  • Shared master data

    Personnel, business-party (customer/supplier), catalog and physical-asset records are kept in one place.

  • Report centre and data transfer

    Reports, exports and import tools are offered at the platform level.

  • Web and mobile

    Management in the web app, field and employee experience in the mobile app.

PERSO One Platform

Let’s shape PERSO around your business, together.

Let’s clarify which products to start with, your branch structure and your field teams, and build a demo plan.