3Edit Web Builder iconLesson 8 · How web apps work

How a website or web app is built

Three areas: public pages, a customer area and an admin area.

Most websites and web apps are built from up to three areas: public pages for every visitor, a customer area for signed-in customers, and an admin area for the owner and staff. Learn which areas your idea needs, and why each one needs sign-in and its own permissions.

About 8 minutes to readLast updated

By Humayun Rashed, founder of 3Edit

The three areas

Think of a shop. The shop floor is open to everyone. Each customer’s receipt and bag belong only to them. The back office, with the till and the stock, is for the owner and the staff. A website or web app is built the same way, from up to three areas.

Not every site needs all three. The sections below show three kinds of site, from the simplest to the biggest.

AreaWho uses itWhat happens there
Public pagesEvery visitor, signed in or notRead about the business, see prices, get in touch, book or buy
Customer areaEach signed-in customerSee and manage their own bookings, orders and details
Admin areaThe owner, and staff with limited accessRun the business: bookings, orders, products and customers

A simple site: public pages only

A café, a plumber, a photographer or a local shop often needs only public pages: what you offer, your prices, your opening hours, your work and how to reach you. Visitors get in touch by email, phone or WhatsApp, with buttons that open their email, their phone or a WhatsApp chat.

Nothing is saved on the site and nobody signs in, so a simple site needs no database. It is the quickest kind to build and the easiest to look after. Does my website need a database? has the test that tells you whether this is your site.

A booking site: all three areas

Now take Fade & Co, a fictional barber shop with three barbers. Its site uses all three areas, and each one is for different people. The booking app project builds a smaller version, with a public booking form and a private owner area.

  1. The public siteAnyone can see the services, prices and barbers, and book an appointment.
  2. The customer areaA signed-in customer sees their own bookings, and can change or cancel them.
  3. The owner areaThe owner sees every booking, sets the services and opening hours, and manages the team.
  4. Staff accessEach barber signs in to see the bookings they need, without the owner’s settings.

An online store: shop, customer area and admin

A store follows the same pattern, with more in each area. The shop pages show the products, the cart and the checkout. In the customer area, each customer sees their own orders, invoices and addresses. The admin area is where the owner adds products, handles orders and sees every customer, and staff roles let each team member open only the parts they work on.

The 3Edit Ecommerce starter kit comes with all three areas. Its customer area has Overview, Orders, Bookings, Addresses, Wishlist and Account Settings pages, and admins can add staff under Settings → Staff, choosing the areas each person can open. The online store project starts from it.

Roles and permissions, in plain words

A role is the kind of user someone is: visitor, customer, staff or owner. A permission is one thing a role is allowed to do, such as “see every booking” or “change prices”. Together they answer one question for every page and every record: who may see this, and who may change it?

Sign-in is how your site knows who someone is. Permissions decide what that person may do once they are in. User login and accounts explains how roles and access rules work in the database.

RoleCan openCan do
VisitorThe public pagesRead, get in touch, book or buy
CustomerThe public pages and their own customer areaManage their own bookings, orders and details
StaffThe admin pages their job needsFor example, see bookings but not change prices
Owner or adminEverythingManage the business, the team and the settings

Why each area needs its own sign-in and permissions

  • The customer area holds personal details: names, phone numbers, addresses and order history. Only the customer they belong to should see them, so the area needs sign-in and a rule that each customer sees only their own.
  • The admin area can change the business: prices, bookings and orders. It needs sign-in and a rule that only the owner, and staff with permission, can open it.
  • Staff need only part of it: giving each person just the areas their job needs keeps everyone’s work simple, and keeps a mistake or a lost password small.
  • A hidden page is not a protected page: a page with no link to it can still be found. The protection is the rule next to the data, checked every time, as User login and accounts explains.

Plan your areas before you build

Before your first prompt, write down your areas and roles in a few lines: which pages are public, what a customer can do in their own area, and what each kind of staff may open. That short list becomes the clearest part of your prompt, and the AI builds the rules together with the pages.

The full sign-in journey, from creating an account to resetting a password, is in The complete login journey.

Try it in 3Edit.

These prompts plan the areas for Fade & Co, a fictional barber shop, before anything is built. Planning needs no database, so you can try them in any new project. When you build the customer and admin areas for real, connect your Supabase first and read User login and accounts, on login and permissions.

The businesses in these prompts are fictional practice examples. When you build for a real business, only ever show real reviews from real customers: invented reviews mislead customers and are against UK consumer law.

  1. 1Map the areas

    I want a website for Fade & Co, a barber shop in Leeds with three barbers. Before you build anything, list the areas the site needs: public pages, a customer area and an admin area. For each area, say who can open it and what they can do there.

  2. 2Roles and permissions

    For Fade & Co, write a table of roles: visitor, customer, barber and owner. For each role, list what they can see and what they can change. Barbers can see bookings but can’t change prices, services or opening hours. Don’t build anything yet.

  3. 3A simple site instead

    Now imagine Fade & Co only wants public pages: services, prices, opening hours, the team, and a contact section where visitors can call, email or message on WhatsApp. Explain what would change: which areas and roles we would no longer need, and whether the site would still need a database.

Read each plan like the owner would. If a role can do something it shouldn’t, say so in your next message: that sentence becomes an access rule when you build.

About the author.

Written by Humayun Rashed, founder of 3Edit. He also runs 3Edit’s free in-person AI website building and vibe coding course in London.

Questions people ask.

Most websites and web apps have up to three areas: public pages for every visitor, a customer area where signed-in customers manage their own bookings or orders, and an admin area where the owner and staff run the business. A simple site has only public pages.

No. If visitors only read about your business and get in touch by email, phone or WhatsApp, nobody needs to sign in, and the site needs no database.

A role is the kind of user someone is, such as customer, staff or owner. A permission is one thing a role may do, such as seeing every booking or changing prices.

Because each area holds different things. The customer area holds personal details that belong to one customer, and the admin area can change the business. Separate permissions let each person open only what their role needs.

Yes, and it’s good practice. Give each person only the areas their job needs. In a store built from the 3Edit Ecommerce starter kit, admins add staff under Settings → Staff and choose the areas each person can open.

Start vibe coding today.

Download 3Edit for Mac or Windows and build your first professional website in minutes.

Download now
macOSWindows