---
title: "Access controls inside your app | OwlMeans"
description: "What a generated app gives its own users: four areas with fixed access, an organization switcher, a people panel for owners and per-record access."
url: "https://owlmeans.com/docs/platform/how-to/users-and-permissions/access-controls-inside-your-app/"
lang: "en"
---

# Access controls inside your app

![](https://owlmeans.com/_astro/platform-how-to-users-and-permissions-access-controls-inside-your-app.DftOtUUo_1ptWMH.webp)

You manage access from the project’s Users view. The app you generate also carries access controls of its own, so a customer’s owners can manage their people without opening the Platform.

## The four areas

Every screen of a generated app lives in one of four areas, and it takes its access from the area.

| Area | Address | Who can open it |
| --- | --- | --- |
| Guest | `/` | Anyone, signed in or not. |
| User | `/frontoffice` | Any signed-in person. |
| Admin | `/admin` | The app’s owner, who holds the admin permission. |
| Operator | `/backoffice` | Staff who run the business process. Individual screens can require a specific permission. |

A visitor who is not signed in sees “Sign in to continue” in a protected area. A signed-in person without the right permission sees the access-denied view. See [How your app’s users sign in](https://owlmeans.com/docs/platform/how-to/users-and-permissions/how-your-app-users-sign-in).

## What owners and members get

When the app keeps records per organization, its screens can include:

-   an organization switcher in the header, shown only to people who belong to more than one organization
-   a people panel where an organization’s owners invite members by email and remove them; an invited person is added at once, signs in and picks the organization, with nothing to accept
-   per-record access, where an owner chooses which members may view or change a particular record; owners hold these permissions for every record by default

## Add these to your app

1.  Describe the people and access needs in a user story, such as “A team owner invites members and chooses who can edit a project.”
2.  Develop the story and open the Preview.
3.  Sign in as an owner and check that the panel invites, removes and grants access.
4.  Sign in as a member and check that only the granted records are available.
5.  Repeat in [Production](https://owlmeans.com/docs/platform/how-to/users-and-permissions/choose-preview-or-production-users) before you launch.

> Organizations do not add an area. A customer’s owners and members work in the User area, or the Operator area for a back office kept per organization. Admin stays with the app’s owner.

See [Build for multiple customer organizations](https://owlmeans.com/docs/platform/how-to/build-for-multiple-customer-organizations) and [Manage organizations and members](https://owlmeans.com/docs/platform/how-to/users-and-permissions/manage-organizations-and-members). Agents can do the Platform side through the [MCP tools](https://owlmeans.com/docs/mcp/reference/application-users-permissions-and-organizations). Back to the [section overview](https://owlmeans.com/docs/platform/how-to/manage-sign-in-users-and-permissions).

## Application example

**Category:** Project and task management. **Example:** Task Grove, a task board for a small team. A customer’s owner invites teammates, and gives one contractor access to a single project’s tasks.
