Travel agencies
Agency with several trips
Keeps each agency's travellers apart on one platform, so one business never sees another's trips.
Platform · Security
Each business's data is kept separate in the database with row-level security. Documents are stored privately, and a download needs a signed-in user.
Aditi
Emergency handoff
Platform
Travel and hotel records hold names, phone numbers, bookings and trip documents. A careless query in a shared system could show one business another business's guests.
How it works
Row-level security in the database limits every query to the business that signed in.
Trip documents and vouchers are stored privately. A download needs a signed-in user.
Turn on two-step verification with an authenticator app for each account.
Medical, accident, police and fire messages are handed to a person at once.
On WhatsApp
A number that is not linked to a trip gets public answers only. Aditi does not share an itinerary with a number that is not on it.
Aditi
Number not linked to a trip
In the portal
Tickets and vouchers are kept in private storage. Staff open them from the portal after signing in, and they are not public links.
Documents · Goa beach week
Flight tickets, outbound.pdf
4 travellers · added 12 Nov
Hotel vouchers, Calangute.pdf
Whole trip · added 12 Nov
Airport transfer, Dabolim.pdf
4 travellers · added 13 Nov
Sunset cruise confirmation.pdf
Day 3 · added 14 Nov
Files are stored privately. Downloads need a signed-in session.
Why teams use it
Row-level security keeps each business's guests, trips and stays in its own rows.
Tickets and vouchers are not public links. A download needs sign-in.
An authenticator app adds a code as a second step at sign-in.
Passwords, tokens and payment details are kept out of application logs.
Emergency messages skip the queue and reach a person, with a fixed reply from Aditi.
Each person sees the parts of the portal their role allows.
Use cases
Agency with several trips
Keeps each agency's travellers apart on one platform, so one business never sees another's trips.
Hotel with guest documents
Keeps stay documents private, so a guest's voucher is never a link anyone can open.
Owner answering a data question
Can see who has which role and how documents are downloaded, without reading any code.
Straight answers
No. Row-level security limits every query to the business that signed in.
In private storage. A download needs a signed-in user, so a file has no public link.
A second step at sign-in: a code from an authenticator app, after your password.
No. Passwords, tokens and payment details are kept out of application logs.
Aditi hands the chat to a person straight away and sends a fixed reply. Your team sees it in the inbox.
Set it up in an afternoon, and check every answer in the test chat before a single traveller or guest writes in.
Getting started