Projects
A project is the top-level home for everything in Fren One: your communities, your analytics, your billing, and your team. Think of it as a workspace that a group of people manage together.
Each person on your team holds one or more roles that determine which parts of the dashboard they can see and what actions they can take.
The roles
| Role | How you get it |
|---|---|
| Owner | Automatically assigned to the person who created the project. There is always exactly one Owner (see below). |
| Project Admin | Granted by the Owner. Has nearly the same capabilities as the Owner — the main difference is they can't permanently delete the project or transfer ownership. |
| Billing Admin | Can view and manage the subscription, but has no access to analytics, AI tools, or team management. |
| Analytics Admin | Can access Analytics, AI Workspace, Reports, and the Inbox — but cannot touch billing or team settings. |
| Verified Admin | A community admin (Discord/Telegram) who has verified their admin status through Fren One. Gets scoped access to the communities they're verified on. |
| Member | On the team but no special privileges. Can view the team list and their own profile. |
One person can hold multiple roles. For example, someone can be both a Billing Admin and an Analytics Admin.
What each role can access
The table below maps each role to the surfaces they can use. "Verified Admin" access is scoped to the specific communities they've verified on.
| Surface | Owner | Project Admin | Billing Admin | Analytics Admin | Verified Admin | Member |
|---|---|---|---|---|---|---|
| View team list | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Invite new members | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ |
| Billing & subscription | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ |
| Analytics, AI Workspace & Reports | ✅ | ✅ | ❌ | ✅ | Scoped ¹ | ❌ |
| Inbox (view) | ✅ | ✅ | ❌ | ✅ | Scoped ¹ | ❌ |
| Inbox (resolve alerts) | ✅ | ✅ | ❌ | ❌ | Scoped ¹ | ❌ |
| Audit log | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ |
| Knowledge base | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ |
| Agent & moderation config | Verified ² | Verified ² | ❌ | ❌ | Scoped ¹ | ❌ |
| Connect / assign / unlink communities | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ |
| Permanently delete a community | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ |
| Restore / import a server backup (Discord) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ |
| Project settings | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ |
| Team management (add/remove/edit roles) | ✅ | ✅ (limited ³) | ❌ | ❌ | ❌ | ❌ |
| Grant or revoke Project Admin | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ |
| Transfer ownership | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ |
| Delete the project | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ |
| Leave the project | ❌ ⁴ | ✅ | ✅ | ✅ | ✅ | ✅ |
¹ Verified Admins see data only for the specific communities where they hold an active verification.
² Configuring the agent for a community requires an active verified admin status on that community.
³ Project Admins can manage Billing Admins, Analytics Admins, and Members — but not other Admins or the Owner.
⁴ The Owner must transfer ownership or delete the project before they can leave.
Why there is exactly one Owner
Every project has precisely one Owner at all times — no more, no less. This matters because some actions are simply too consequential to be shared: transferring the project to someone else, permanently deleting a community, and deleting the project itself. Having a single, clearly identified Owner means there is always one person who is accountable for those decisions.
If you need someone to have broad management access without giving up ownership, make them a Project Admin — they can do nearly everything the Owner can.
To give someone admin-level access without handing over your project, go to Settings → Team, find the member, and promote them to Project Admin.
What only the Owner can do
A few actions are reserved for the Owner alone:
- Transfer ownership to a Project Admin (the recipient must accept)
- Grant or revoke the Project Admin role
- Permanently delete a community from the platform
- Restore or import a Discord server backup — this recreates or overwrites the entire server, so it follows the same principle as permanent deletion
- Delete the entire project
Everything else that requires elevated access — including billing, analytics, agent config, and community management — can be delegated through the other roles.
Next steps
- Community Lifecycle — understand the states a community can be in
- Ownership & Teams — how to transfer ownership, invite members, and leave a project
- Billing & Payers — who pays, and what happens when that changes