Named accounts
Avoid shared employee credentials wherever possible.
Security, data and access
Understand how your team and business information are managed before launch.
Ledgez supports controlled employee access and a centralized business record. Hosting, backup, retention and recovery details are deployment-specific and should be documented clearly during implementation.
This page intentionally avoids vague security claims. Deployment details should be confirmed in writing for the environment selected by each customer.
Access control
Give employees the information required for their role.
Sales, office, production and accounting users do not always need the same access. User permissions can be configured around responsibilities and reviewed as the team changes.
Role-based access
Limit functions and information according to job responsibilities.
Access changes
Review permissions when employees change roles or leave the company.
Accounting separation
Provide bookkeeping and financial access only to appropriate users.
Deployment documentation
Ask for specific answers, not a generic “secure” label.
The exact technical answer can depend on the hosting and deployment selected. Before launch, the implementation documentation should identify the practices that apply to your account.
- Hosting provider and data location
- HTTPS and encryption practices
- Backup frequency, retention and restoration process
- Password and user-account policies
- Support access and escalation procedures
- Data export and account-termination process
Questions to resolve before go-live
Who can administer users? How often is the environment backed up? How is a restoration requested? What data can be exported? How is access removed? These details should be part of the implementation record rather than assumptions.
Payment information
Keep using the payment processor selected by your business.
Ledgez can record and allocate customer payments while the card transaction remains with the chosen processor. Processor-specific security, fees and card-data handling remain governed by that provider.
Reduce uncontrolled copies
One connected record can reduce spreadsheet and email duplication.
Centralizing customer, order, purchasing and accounting information can reduce the need for employees to maintain competing versions in personal files. Internal policies and responsible user behavior remain important.
Shared responsibility
Software controls and company practices work together.
Ledgez and hosting
Provide the documented platform, deployment, backup and support practices agreed for the account.
Customer administrators
Manage employees, permissions, password expectations and timely removal of access.
Individual users
Protect credentials, use approved devices and avoid exporting or sharing information unnecessarily.
Questions to ask
Security and data questions deserve direct answers.
Does Ledgez support different employee permissions?
Yes. Access can be configured by user so sales, office, production and accounting personnel work with the functions relevant to their responsibilities.
Where is customer data hosted?
Hosting and data-location details depend on the selected deployment. The applicable provider and location should be documented before launch.
How are backups handled?
The backup schedule, retention period and restoration process are deployment-specific and should be included in the implementation or service documentation.
Does Ledgez store credit-card information?
Ledgez can record and allocate payments while the transaction is handled by the company’s selected payment processor. Processor-specific card-data handling should be confirmed with that provider and the final deployment configuration.
Can business data be exported?
Required exports, migration deliverables and account-termination procedures should be defined during implementation and reflected in the service agreement.
Review the details before implementation
Bring your security, access and data questions to the discovery call.
We can identify the specific deployment documentation your business requires before configuration and migration begin.