A separate business instance
Panelane's current deployment model gives each business its own application deployment and database. The marketing website is separate from the business workspace. Hosting arrangements, region, domain ownership and administrator responsibilities are agreed during onboarding.
This is an architecture description, not a certification claim. Ask to see the access and recovery arrangements for the environment you will actually use.
Access follows the job
Counter staff, workshop staff, drivers and managers need different permissions. Set up named staff access, check who can change prices or approve refunds, and remove access when roles change. Avoid sharing manager credentials to work around a missing permission.
Google sign-in, where configured, is an authentication option. It does not itself grant a staff role, trade approval or permission to access another business. Account recovery must follow the workspace's verified identity process.
Payments and connected services
Card payment collection uses the configured payment provider. Staff should never copy card details into customer notes or email. A payment attempt, an authorisation and a settled payment are different states; reconcile against the provider when a result is uncertain.
Accounting, email and other connections require the relevant business account, permissions and configuration. Agree who owns those accounts and how access is revoked at the end of service.
Backup is only half of recovery
Your hosting proposal should identify what is backed up, where the copies are kept, how long they remain, who receives failure alerts and the expected recovery process. Ask when a restore was last demonstrated for the deployed setup.
A completed backup job does not prove every recovery step. Before trading, agree the response to a lost server, an accidental change and a provider outage. The contract, not this page, sets recovery and availability commitments.
Documents, exports and ending service
Agree the export formats and scope for your customers, catalogue, orders and documents. An export is useful only if the receiving system can understand it; check representative files during onboarding.
Retention, deletion, assistance and any transition charges belong in the service agreement. Separate public website enquiries from the customer records your business controls.
Report an access or security concern
Use the support channel in your agreement or support@quantumaiwebapps.com. Include the affected business, page, approximate time and a description. Do not include passwords, secret keys or customer payment details. If a staff device is lost, tell your workspace administrator promptly so access can be reviewed.