Frequently Asked Questions
Our agency or manager was let go — how do we take our community back?
You can detach the community yourself, as long as you have verified admin access on Discord or Telegram. You don't need to be part of the agency's project at all. Go to the community's Fren One page, scroll to the Danger zone, and click Detach from project — Fren One will confirm your admin status live and then release the community immediately. You can optionally move it straight into your own project in the same step. See Detaching Communities for the full walkthrough.
Can someone who left the project still see our data?
No. The moment someone leaves (or is removed from) the project, they lose access to the dashboard, analytics, Inbox, AI Workspace, and all other project surfaces. Their Fren One account still exists, but they simply have no access to your project's data.
What happens to our data when a community leaves a project?
The key rule is: community history travels with the community; project records stay with the project. The community's full analytics and activity history become invisible to the old project but are available in full to any project that claims the community. Your project keeps its own reports, audit log, AI conversation threads, knowledge base entries, and inbox resolutions — those are records of what your project did, and they never move. See Detaching Communities for the complete breakdown.
Does a new project see the community's old history?
Yes. A project that claims a previously detached community gets the community's complete history — all past analytics, member activity, and moderation records — from before, during, and after the previous project's era. This is intentional: that history belongs to the community, not to any particular project.
Nobody on the project is an admin of the community anymore — what happens?
If your project loses all verified admin coverage for a community — meaning no current team member holds an active verified admin status for it — the 30-day coverage countdown begins. You'll get a warning on day 0 and a final warning on day 23. Any team member can stop the clock at any time by re-verifying their admin access. If nobody acts by day 30, the community is automatically detached and notified admins elsewhere on the platform can claim it. See Community Lifecycle for the full timeline.
The agent was removed from our group — does the 30-day countdown start?
No. The coverage countdown only advances based on confirmed information from Discord or Telegram. When the agent is removed or unreachable, the platform can't get a definitive answer about admin status, so all timers are frozen. The countdown starts (or advances) only when the platform receives a clear, definitive response about who does or doesn't have admin access. An agent outage will never trigger an auto-detach.
Can a project have two Owners?
No. Every project has exactly one Owner at all times — this is enforced by the platform, not just a policy. If you need someone to have near-equivalent access, make them a Project Admin: they can do almost everything the Owner can, with the exception of transferring ownership, permanently deleting communities, and deleting the project itself.
I left a project by accident — how do I get back in?
You'll need someone on the project (an Owner or Project Admin) to send you a new invitation. There's no self-serve re-join path after leaving — this is intentional so that project owners always control who has access. Once you accept the new invitation, your access is fully restored based on the role you're invited with.
What happens when the Owner deletes their account?
Ownership passes automatically to the most appropriate remaining team member — prioritising Project Admins, then other members by community coverage and tenure. The new Owner receives an email explaining the situation and is given a clear path to transfer ownership to someone else or delete the project if they don't want the responsibility. The departed owner's billing card is not charged past their current billing period; the subscription is set to cancel at period end, and billing-capable members are notified so someone can take over before it lapses.
What's the difference between "detached" and "deleted"?
A detached community is still fully intact — its configuration, agent setup, and history are all preserved. It's simply no longer connected to any project. Any verified admin can claim it at any time, and there's no expiry. A deleted community is gone permanently; there is no recovery path. Deletion can only be triggered by the project Owner explicitly choosing to permanently delete the community, or by a recovery window expiring with no admin re-verifying in time.
Who gets charged after an ownership transfer?
The subscription does not move automatically with ownership. Whoever was the payer before the transfer continues to be the payer afterward (as a Project Admin). If the outgoing Owner chose to cancel the subscription during the transfer, the subscription ends at the current period boundary and billing-capable members can initiate a takeover. See Billing & Payers for details on how the takeover works.
Why can't I remove this team member?
If a team member is a verified admin of at least one community in your project, you can't remove them while that verification is active. This rule exists to prevent a project from being locked without any admin coverage — removing the last verified admin of a community would immediately start the 30-day countdown. To remove the member, they would first need to be replaced by another verified admin on those communities, or the communities would need to be unlinked from the project first. You'll see an explanation in the UI when a removal is blocked.
Still have questions?
Check the other pages in this section: