Now booking new clients Lake Charles, Louisiana
Free resources › Client portal permissions
Free download

Let customers watch the job, not the chatter.

The outline from our video on permission levels: how one app gives the owner, the office, the crew, and the customer each their own view, without handing anyone the whole farm. Download it and hand the folder to Claude: it asks who logs in to your app and what each of them should see, writes that down on one page with you, and builds it once you say yes. Made in Lake Charles, Louisiana.

Get the download

We'll email you the link. It's free, and the files are yours to keep.

The link comes from nick@redwaterrev.com. You'll also get our newsletter on using AI in a local business. Every one of those emails has a one-click unsubscribe. This browser remembers your email, so your next download is one click. See our privacy policy.

The four rooms

Think of your software as a building full of doors.

Every page, field, and button is a door. Each person who logs in carries a ring of keys. We plan every portal around four rooms.

1. Who logs in

Four kinds of login

The owner and the office get everything. The crew logs their work and reads the internal notes. The customer sees progress and a PDF. One or two people on the customer's side get a deeper look. Nobody signs themselves up: the office creates every login.

2. Ticks per login

One tick per key

“Can see the daily log” and “can see internal notes” are two different ticks. Read and write are different ticks. New ticks start off until the office turns them on, and the office can preview the app as any login.

3. The server decides

A cut copy, every click

Who is this? What keys do they have? Then it asks the database for only that slice and sends nothing else. The database holds the same rules underneath, so a page built wrong someday still can't hand over a row it shouldn't.

4. What they see

Watch the job, not the chatter

Job progress, a report to download, approve or hold items, and a button to report a problem, so customers aren't calling your phone to ask where things stand.

Under the hood

Never hide it on the screen. Don't send it at all.

The tempting shortcut is one page for everybody with the private parts painted over. But if the data reached their phone, there are ways to peel the paint back. So the cut happens before anything leaves.

One request, start to finish

Sign inThe customer signs in and taps “show me the daily log.”
The checkThe server asks who this is and reads their ticks: daily log yes, internal notes no.
The databaseIt reads the log without the notes, and its own rules agree.
The cut copyOnly that copy reaches their screen. The notes were never in it.
What's in the download

Hand the folder to your AI. It builds from your answers.

ai-client-portal-permissions/the folder you download
├─ START-HERE-FOR-YOUR-AI.mdyour AI asks who logs in and what they see, then builds it with you
├─ permission-blueprint.mdthe four rooms, one request under the hood, and the build order
├─ permissions-sheet.mdlogins down the side, doors across the top, a tick where they get in
├─ test-it.mdnine checks to run before anyone outside the office logs in
└─ README.mda one-minute start

Unzip it into your app's project, open the folder in Claude Code (the Claude desktop app's Code tab is the easiest way in), and type:

Read START-HERE-FOR-YOUR-AI.md and help me set up permission levels for my app.
Who it's for

Owners who want customers in the loop without opening the books.

We're two brothers in Lake Charles who build custom software for local businesses. The drawings in the video come from a real job-tracking app we built for an industrial services company. This download fits any business building its own app or portal with AI, from tree services and contractors to inspection firms, where the crew, the office, and the customer each need a different view.

Want to see what we build for paying clients? Look through our work.

Questions

Common questions.

Is it really free?

Yes. No card and no trial. The files are yours to keep and change.

Do I need to know how to code?

No. The files are plain English. Your AI asks you who logs in and what they should see, and it writes the code. You answer in your own words.

What do I need to get started?

A computer, a Claude account, and an app to put it in (or a plan for one). Claude Code comes with the paid Claude plans, and the Claude desktop app's Code tab is the easiest way in.

Does this make my app secure?

It's how we plan permissions, not a security review. The test list catches the common mistakes, and you should still have someone you trust look at any app that holds customer data before real people log in.

Can Redwater build this for my business?

Yes. We're based in Lake Charles and build custom portals like this for local businesses. Book an AI audit and we'll tell you honestly whether it's worth it for you.

Want a portal like this for your customers?

Start with an AI audit. We'll look at who needs to see what in your business and tell you honestly whether custom software is worth it for you.

Book your AI audit →