Detaching Communities
A community belongs to its admins, not to whoever manages it on Fren One. If the agency, manager, or project team that brought your community onto the platform is no longer the right fit — or has been let go — you can detach the community from their project and take it with you.
Who can detach a community
You can detach a community if you are a verified admin of that community right now. Specifically:
- You must have previously verified your admin status with Fren One (through the join or verify flow).
- At the moment you click Detach, Fren One makes a live check with Discord or Telegram to confirm you still have admin access. If your status has changed, the detach is blocked.
You do not need to be a member of the project that currently manages the community. This is intentional — a fired agency still owns the project; you might have no access to it at all.
If you've never verified your admin status with Fren One, start by connecting your account (via the "Join a project" or "Claim a community" flow). The verification happens there, and once confirmed, you can proceed to detach.
How to detach
- Open the community's settings page in Fren One (or find it through the "Communities you manage" view).
- Scroll to the Danger zone at the bottom.
- Click Detach from project. Fren One confirms your admin status live before showing the confirmation.
- Optionally, choose a project of yours to move the community into immediately. This happens atomically — the community moves from one project to the other in a single step, with no window where it's unowned.
- Confirm. The detach completes instantly.
If you're the project Owner (not an outside admin), the same action is available as "Unlink" — the effect is identical, just through a different label because you're acting from inside the project.
What happens to your data
This is the most important part. Data ownership follows a clear rule: community history travels with the community; project-specific records stay with the project.
| What | What happens on detach |
|---|---|
| Live analytics, Inbox, AI Workspace | Immediately removed from the old project's view. If claimed into a new project, accessible there right away. |
| Historical analytics & activity (all past events and metrics) | Hidden from the old project. Fully visible to any future project that claims the community. Nothing is deleted. |
| Old project's reports, audit log, and AI conversation history | Stay with the old project permanently. These are project records, not community records. |
| Knowledge base | Stays with the old project. The community starts fresh in any new project. |
| Agent configuration (moderation rules, welcome messages, etc.) | Stays with the community. The agent keeps running with exactly the same settings. |
| Premium features | Drop to free immediately upon detach (no project = free tier). If claimed into a project with an active subscription, premium features restore right away. |
Your community's member activity, moderation history, and analytics belong to your community — they're a record of what happened there, not a record of what any particular project did. A new project claiming your community should be able to see that full context.
The 30-day automatic detach
Even if no one on the community side takes action, there's an automatic backstop to protect your community.
If your project has no team member with an active verified admin status for a community — but verified admins exist elsewhere on the platform — the platform starts a 30-day countdown:
| Timeline | What happens |
|---|---|
| Day 0 | A warning alert appears in the project Inbox and the Owner gets an email. Any current project member can re-verify to stop the clock. |
| Day 23 | A final warning is sent. |
| Day 30 | The community is automatically detached. Every verified admin of that community on the platform is notified that it's available to claim. |
The 30-day clock only advances based on confirmed information from Discord or Telegram. If the agent is unreachable, the countdown is frozen. You won't lose a community just because the agent had a rough week.
The auto-detach takes the same data-handling path as a manual detach — history stays with the community, project records stay with the project.
Claiming a detached community
A detached community is unclaimed and available to any verified admin on the platform. To claim it:
- Connect your Fren One account if you haven't already.
- Your verified communities show up in the "Claim a community" flow.
- Select the community and the project you want to move it into — a project where you are the Owner or a Project Admin (or create a new one on the spot).
- Done — all historical analytics and activity become available in your project immediately.
There's no expiry on a detached community. It stays claimable until someone picks it up.
What the old project owner sees
The project Owner is notified when their community is detached. For privacy, the notification does not name the person who detached it — only that the community has left the project. The full audit record (including the actor's name) is preserved in the project's audit log for the Owner's reference.
Next steps
- Community Lifecycle — the full state diagram and what each state means
- Billing & Payers — premium features and what detach means for your subscription
- FAQ — "Our agency was let go — how do we take our community back?"