Share only what the customer should see

Customer Portal Security

Customer portal links separate selector and validator values, store only validator hashes and apply customer/company scoping to shared records.

What this covers

Portal access uses expiring, revocable token patterns.

Customer portal links separate selector and validator values, store only validator hashes and apply customer/company scoping to shared records.

01Random token generation

Connected to the wider MAS ERP process and controlled by company feature selection and permissions.

02Hashed validator storage

Connected to the wider MAS ERP process and controlled by company feature selection and permissions.

03Expiry and revocation

Connected to the wider MAS ERP process and controlled by company feature selection and permissions.

04No-store and no-index headers

Connected to the wider MAS ERP process and controlled by company feature selection and permissions.

05Portal activity evidence

Connected to the wider MAS ERP process and controlled by company feature selection and permissions.

Expected outcomes

What better operating control should deliver

Safer customer self-service
Reduced credential exposure
Traceable access
Plan your MAS ERP journey

See how MAS ERP fits your operating model.

Tell us about your companies, users, workforce and priority modules. We’ll prepare a focused product conversation.