01
Access by role
Customers, account admins, sales reps, and your team see the information they need for their job.
Security for the ERP front office
Trust / Security
Security is not a page. It is part of the system.
Role-based access, SSO/MFA, tokenized payments, and encrypted ERP sync built in from day one.
Preview
The short version
Security starts at the edge.
- The ERP holds the facts.
- People get only the access they need.
- Data is locked as it moves.
- Payments use secure codes, and card data is not stored.
- Changes are checked and recorded.
- Your data stays yours.
01 / Where data lives
The ERP holds the facts. The website sits at the edge.
The question is not just 'is the site secure?' It is 'who can see which price, account, order, and document?'
The point
Every connection is a choice about access.
Nomad connects your store, catalog, configurator, and portal to your ERP — enforcing every account and price rule.
Your ERP owns the records. Nomad owns the storefront. Role permissions control every view.
See the ERP connection02 / Access and sign-in
The right person, account, and data.
Access is part of the plan, not a late add.
02
Only the access they need
Admin access is separate from customer access and is reviewed during setup.
03
Sign-in options
We can connect to your single sign-on (SSO) provider and support multi-factor authentication (MFA), then confirm which options fit your setup.
03 / Data and payments
Protect the data and limit the damage.
The safest payment setup keeps card data out of your system.
01
Data is locked as it moves
Data protection protects information as it moves between the browser, our system, and other tools.
02
Secure payment codes
Payment providers use secure codes, so card information stays out of your website.
03
Your data stays yours
Customer, order, and product information stay yours, and you can request the current data map and export.
04 / Operations & monitoring
Security is also how we run the system.
Checks only help if people use them.
01
Watching and records
We watch the website and keep records so we can look into problems.
02
Review of changes
We check and test each change before it goes live.
03
When something goes wrong
We set the steps for who to call, what to say, and how to recover before a problem occurs.
05 / What we share
Ask for the paperwork, not a badge.
We do not claim certificates on this page. Request current paperwork, data maps, and details about outside suppliers, and bring them to your review.
Your security review kit
What we can cover
- How the connection works and how data moves.
- Sign-in and who can do what.
- Payments and where card data stops.
- Where data is hosted, backups, and recovery.
- How we review changes and handle problems.
- Outside suppliers and current security paperwork.
06 / Questions
A short list of questions.
Start here, then bring your own needs.
Payments are tokenized through PCI-compliant gateways — raw card numbers never touch your store.
It depends on your setup and identity provider, so bring your SSO and MFA requirements to the working session.
Hosting and outside suppliers depend on the setup, so request the current data map and hosting paperwork.
The ERP connection uses its own sign-in with only the access it needs, and we record and change that access on a set schedule.
07 / Run the review
Bring the checklist, and we will bring the data map.
Use the review kit to cover access, data, and payments with your team. Cover ongoing operations and monitoring too.
The next moveBring your security team, and
Bring your security team, and
we will bring the plan.
Walk through how information moves and who can see what with the people who will run the system. Bring your open questions.