Implementation and piloting
Getting started, migrating data and accepting the deployment.
We collected questions about implementation, applications, services for residents, payments and security. The responses describe the current scope of the pilot and its limitations. If something is missing, please write to us.

Getting started, migrating data and accepting the deployment.
Daily work for drivers and field teams, offline mode and location access.
Schedules, reports, bookings and accounts.
Stripe, Przelewy24, Fakturownia and subscriptions.
Organizational isolation, MFA, audit and backups.
Questions are grouped by area.
Solution pages describe the working scope and requirements.
The contact form will assign a case number to the service center.
From a conversation and presentation on a scenario similar to the work of your team. Then we determine the scope of the pilot and acceptance criteria.
CSV import. The system shows a preview, validates fields and indicates duplicates before saving.
Each organization works with its own data, isolated from other organizations through RLS. We import production data after the organization’s approval.
Agreed acceptance criteria, connection to LifeNexa CORE, a data processing agreement, security testing and the required provider connections.
Yes. We determine the scope with the organization, for example only PSZOK and the resident portal or only NexaWorks.
The daily plan, assigned collections and tasks, addresses, waste streams, checklists and documents. Completion is confirmed with weight, notes or photos.
Text changes are placed in an encrypted queue and sent when the connection is restored. Photos require a connection to the server.
If the record has changed on the server, the application shows a conflict. The user decides whether to discard his change or open the current record.
No. Location is accessed only on request, after the user grants the system permission. There is no background tracking.
The iOS code is ready, but the app has not been built or published yet.
No, to check the schedule. An account is needed for applications, reservations, payments and notifications.
The resident selects a free date and receives a code to present. The operator confirms the authorization to use the point in advance.
By booking an appointment on the portal or application. The pickup goes to the driver's route, and once completed, it undergoes inspection.
Notifications now work in the app. SMS, email and push require a provider connection.
The guide has five waste streams, 18 examples and links to materials from the Ministry of Climate and Environment. Local municipality rules prevail.
Stripe and Przelewy24, after your organization has set up your accounts. The available methods depend on the agreement with the payment operator.
Organization administrator, after logging in with MFA. The keys are encrypted on the server and are not displayed later.
In the Fakturownia: manually from receivables or automatically after confirmed payment, if the administrator enables this option.
KSeF integration has not yet passed acceptance testing. It requires a separate workflow and verification.
The subscription covers use of the platform. A municipal-service charge is an amount payable by a customer or resident. These are separate billing processes.
Via RLS in the database and permission checking in the API. The organization is determined from the user session.
Passwords are stored as scrypt hashes and administrators use MFA. The session token is saved in the database only as a SHA-256 hash.
The app account cannot edit or delete history. An audit is a chain of hashes, but it is not a qualified signature.
Yes. Backup restoration has been tested in practice. The production continuity plan is agreed during implementation.
No. Independent penetration testing and regulatory review are pre-production conditions.
Choose a product and a conversation topic. The request will receive a number and go to the service center; We will respond to the address provided.