Governance & Teams

Accountability your stakeholders can see

Fren One gives you the governance infrastructure that tech communities, brands, and agencies need: separated roles, verified admins, a tamper-evident audit log, and a project inbox so nothing slips through the cracks.

Start for freeBook a demo
Built for

Teams that answer to someone

When you operate a community on behalf of a protocol, a brand, or a client, you need to demonstrate control, not just claim it.

Tech communities

Show governance participants that admins are verified and every config change is logged.

Agencies

Run multiple client communities from one workspace, with clear role separation per client.

Enterprise brands

Meet internal IT audit requirements with a tamper-evident log and role-based access controls.

Role system

Separate concerns, not just access levels

Most platforms have a single admin toggle. Fren One governance is a ladder with one level per member: the Owner controls everything, Project Admins run everything except ownership, and every Member can read the whole project. Write access to a community is earned by verification, not asserted.

Roles that don't overlapThe owner controls everything, project admins get everything but ownership, and members read the project until they verify a community to configure its agent.
Every change leaves a recordConfig changes, team actions and community events land in a tamper-evident log with the actor, the timestamp and what it was before.
Alerts before they become incidentsRaids, credit thresholds, verification lapses and bot health all queue in one place — critical on by default, info opt-in.
Accountability

Proof, not promises

Access that expires before stale trust does

Admin rights are re-checked against the live bot service. If a check hasn't passed in 72 hours, access pauses on its own and the first passing check restores it.

A record every change leaves behind

Config changes, team actions and community events are logged with actor, timestamp and before/after state — so "who changed that setting?" has an answer.

Alerts before they become incidents

Raids, credit thresholds, verification lapses and bot health queue in one inbox, routed per event to in-app, email and push.

Role permissions

Who can do what

One level per member: Owner, Project Admin, or Member. Agent access is earned by verifying admin rights in each community — Owners included.

SectionOwnerProject AdminMember
Analytics, Reports & AI Workspace✓✓✓
Audit log✓✓✓
Inbox✓✓View · resolve where verified
Billing & subscription✓✓—
Team management✓Members only—
Community connections & settings✓✓—
Agent config & moderationVerified communitiesVerified communitiesVerified communities
Delete project · transfer ownership✓——
All governance features

The complete governance toolkit

Project workspaces

Group communities under a project. Invite the right people, assign the right roles, and keep configuration isolated per project.

Governance ladder

Owner, Project Admin, Member: exactly one level per person, with per-community verification layered on top.

Verified-admin system

Community admin access is granted only after the bot confirms the claim in-platform, then re-confirms it within 72 hours.

Freshness re-checks

Automatic background re-verification. Stale access pauses; the first positive signal restores it.

Full audit log

Tamper-evident record of every change (actor, timestamp, before/after state), filterable and exportable.

Project inbox

Unified alert queue: raids, credit warnings, verification lapses, agent health issues, all in one place.

Team invitations

Invite teammates by email, assign a role at invite time, and revoke access in one click.

Protected members

Mark key community members as protected so no automated action can remove or mute them without manual override.

FAQ

Common questions

A Project Admin can do everything the Owner can except delete the project, transfer ownership, manage other Project Admins, and permanently delete communities. Every project has exactly one Owner, and ownership changes only through the explicit transfer flow, never by editing a role.
Every project member has read access to the project-wide data surfaces: analytics, reports, the AI Workspace, the inbox, the knowledge base, and the audit log. Write access is earned, not assumed: a Member verifies their admin rights in a community to configure its agent and use its moderation tools. Governance can also hand a Member specific extra capabilities, like ticket handling, as individual grants.
Access to the sections gated on community admin status (agent configuration and moderation tools) pauses automatically after 72 hours without a passing verification check. The account is not deleted or demoted; access resumes the moment a successful check completes, either from the automatic background sweep or by clicking Re-verify.
During the free open beta, the full audit log is available to every community. It will likely be part of higher tiers once paid plans launch, but exact plans and pricing are still being finalized.
Yes. One Fren One account can own or be a member of multiple projects. Each project has its own community list, team, and settings.

Give your team the structure it needs

Start with roles and grow into governance.

Start for freeBook a demo