Each campsite’s data, separated in the database
Camppy keeps each campsite’s data apart inside the database itself, and every person sees and changes only what their role allows. Here is how that works.
Separated at the database level
Separation per campsite is enforced by row-level security in PostgreSQL: a rule inside the database itself that applies to every request and every role, not a filter in the app.
Someone who works for several campsites switches between those they have access to from the same account, and sees data and permissions for the active campsite only. All data moving between phones, browsers and the server is encrypted.
Everyone sees what their job needs
Administrator, supervisor, technician, cleaner and unit owner each have their own views and permissions. What a person may see and change is set by their role and enforced on the server.
- An owner sees only their own units, bookings and statements, never another owner’s, even when several owners share a unit.
- Prices for cleaning, tasks, extras and gas are seen by the administrator and by the unit owner for their own statement. Staff who do or check the work do not see them.
- A team or person limited to certain locations and buildings gets no work outside them, not even by hand, and sees no gas requests or notifications from there.
- Photos from a cleaning are seen by the administrator, the supervisor before approval and the team holding the job. By default they are kept for 60 days.
Signing in
An administrator who signs in with a password then enters a six-digit code sent by email. Until the code is entered, no campsite data is shown.
Cleaners, supervisors and technicians sign in with a four-digit PIN on their own linked device, without an email address or password. The device is linked with a PIN link sent by the manager, and after several wrong PINs it is disconnected.
- Invitations can be sent, resent and revoked. A person becomes an administrator only after accepting an invitation sent by email.
- A team member who leaves is archived: they lose access to the app, and their name stays on the work they did.
Completed work is not deleted
A submitted or completed cleaning, a completed task and a gas delivery cannot be deleted, so reports, statements and history stay complete. A unit with completed work or past stays cannot be deleted either.
The activity log shows the administrator who did what in the field: cleanings, checks, guest departures, gas and data changes, with search and filters. Camppy also records the start, handover, check, rework and block of every cleaning and who was on the team.
About security
Does a cleaner see prices?
No. Prices are seen only by the administrator and by the unit owner for their own statement. A cleaner opens the app and sees their own list for today.
What happens when someone leaves the team?
A team member who has worked at the campsite is archived rather than deleted: they lose access to the app and disappear from lists, teams and the schedule, while their name stays on completed work, in reports and in history.
Can a cleaning be deleted after it has been done?
No. A submitted or completed cleaning has no delete option, so reports and owner statements stay complete. A cleaning that is still open can be cancelled, and it stays in the unit’s history.
Tell us how you organise cleaning today.
Your units, your teams, the booking system you use, how you build the daily schedule. We'll reply with a package recommendation and a quote.
- We set Camppy up for you
- Start with the cleaning schedule, add the rest later
We'll reply within one business day.