---
title: "App users"
description: "Manage the end users who sign in to your published template app."
url: https://evonx.ai/docs/launch/app-users
locale: en
updated: 2026-09-04
---

# App users

Manage the end users who sign in to your published template app.

Template apps keep their sign-in accounts in a managed tenant. The **Users** tab
on the project is where you see those people, add new ones, and switch between
the live app and the development copy.

> **Note**
> This tab is for **template** apps (bookkeeping, CRM, appointments, and the rest
> of the catalog). An imported GitHub repository keeps users wherever its own code
> put them — Evonx will not guess at a table and call it "users".

## What you can do

1. Open the project and go to **Users**. Pick **Live** or **Development** —
   live is the people on your published app; development is the copy used in
   previews.

2. Search by name or email, open a row for details, and scan the sign-ups chart
   to see whether new accounts are arriving.

3. Add a user when someone needs access before they self-register: choose how
   they sign in, set their role if the template has one, and save.

Roles and what each person can do inside the app still come from the template
(and from later [Evolution Threads](/docs/evolve/evolution-threads) that change
it). The Users tab manages the *accounts*; the app itself enforces the
permissions.

## When someone leaves

Deactivate or remove their account the same day. That is the habit that closes
the most common real-world hole. More on your own Evonx login:
[Account & security](/docs/trust/account-and-security).

## Related

- [Start from a template](/docs/build/start-from-a-template) — which apps have
  this tab.
- [Managed database](/docs/launch/managed-database) — users are rows in the
  tenant database; the Database tab is the wider view.