# Sign-in

Sign-in decides who comes in: visitors, your users, or your team. Page Lemon runs the sign-in; there's nothing to set up yourself.

## Say this to your AI

```prompt
Make my site invite-only and let in alex@example.com
```

```prompt
Let my clients sign in on my PageLemon.com site, send me requests, and see my replies
```

## Who comes in

| Who | How they get in | Used for |
|---|---|---|
| **Visitors** | No sign-in, or a passcode you share | A public website, or a private one behind a passcode |
| **Users:** your customers or members | Their email and a one-time code, on your site's sign-in page | Invite-only sites, and apps where each user keeps their own records |
| **Team:** your people | Their Page Lemon login | Changing and reviewing your sites, Staging copies and private drafts |

A site lets in visitors or users.

Who signs in is half the story: each [list](/docs/lists) then says who sees which records.

## Go deeper

- Visitors and users: [Passcodes and invite-only](/docs/private-sites) · [Apps](/docs/apps) · [Scan users](/docs/scan-members)
- Your team: [Site Developers](/docs/co-editors) · [Workspaces](/docs/workspaces) · [Staging copies](/docs/staging)

**Examples:** [a members' area](/use-cases/members-area), [a client portal](/use-cases/client-portal), [an expense app](/use-cases/expense-app). More [app ideas](/use-cases/apps). For your team: five working [internal tool samples](/docs/internal-tools).

Something not right? See [Fix a problem](/docs/fix-a-problem).

For AI assistants: the guide to every block is at [pagelemon.com/agents/blocks](https://pagelemon.com/agents/blocks).