Workspaces
A workspace is what your team shares in Fren One. It holds your channels (each connected Telegram group, Discord server, X account or subreddit), analytics, billing and team.
What Fren One used to call a project is now a workspace, a connected community is now a channel, and the AI Workspace is now Ask AI. Workspace addresses changed too: app.fren.one/p/<slug> is now app.fren.one/<slug>, and old links redirect.
Getting in
There are three ways onto a workspace with a seat, plus one way in as a channel admin. Joining a Workspace has the steps for each.
| Way in | Level you get |
|---|---|
| An invitation | Member by default, optionally with capability grants. Admin if the Owner invites you as one. |
| An approved company email domain | Member, always. |
| A request, once the Owner or an Admin approves it | Member, always. |
| Verifying as a Telegram or Discord admin of one of the workspace's channels | Channel admin, until someone gives you a seat. |
What decides your access
Three separate things add up to what you can do, and the result can differ from one channel to the next:
- Your governance level: Owner, Admin or Member (or Channel admin, if you have no seat yet).
- Any capability grants you hold.
- The channel verifications you've earned.
Who Can Do What has the full matrix.
Governance level
Everyone on the workspace has exactly one level. Each level includes everything below it.
| Level | How you get it | What it adds |
|---|---|---|
| Owner | You created the workspace, or you accepted an ownership transfer. There is always exactly one Owner. | Everything an Admin can do, plus: deleting the workspace, transferring ownership, granting or revoking Admin, permanently deleting a channel, restoring or importing a Discord server backup, and seeing each team member's two-factor authentication status. |
| Admin | Granted by the Owner, either by promoting a Member or by inviting you as an Admin. | Day-to-day management: inviting and managing members, assigning capability grants, billing, connecting and unlinking channels, editing workspace settings, resolving inbox alerts, and routing alerts to Slack, Discord and Telegram destinations. |
| Member | Everyone else with a seat. Auto-join and approved requests always land here, and so does an invitation unless the Owner chose Admin. | Read access to every workspace-wide data surface: analytics, Ask AI, reports, inbox, knowledge base, audit log, the team roster, and workspace settings. Members create, schedule and share their own reports. |
| Channel admin | You joined by verifying as an admin of one of the workspace's Telegram groups or Discord servers, and nobody has given you a seat yet. | Everything stays narrowed to the channels you're verified on: their analytics, inbox, Ask AI, reports and audit log, and their agent configuration. No grants apply, and the Team, workspace settings and Integrations pages aren't shown. See Channel admins. |
To make someone an Admin, the Owner opens the workspace switcher at the top of the sidebar, selects Workspace settings, then Team, finds the member, selects Manage Access, and sets their role to Admin. Ownership transfers are covered in Ownership & Teams.
"Billing Admin" and "Analytics Admin" no longer exist. Billing is part of the Owner and Admin levels, and every member can read analytics. Anyone who held one of those roles is now a Member; promote them to Admin if they still need billing access. The level once called Project Admin is now simply Admin.
Capability grants
A grant gives a Member one specific kind of write access without promoting them. A Member can hold any number of grants. Owners and Admins already hold every grant through their level. Channel admins can't hold grants.
| Grant | What it unlocks | Notes |
|---|---|---|
| + Tickets | The unified ticket queue for the whole workspace: view, claim, reply to, resolve and assign tickets in every channel, with no per-channel verification. | For a Member, the way to answer tickets in a channel they haven't verified on. |
| + X | Every X configuration page for the workspace's X accounts: Messages, Listening, Safety, and Agent Settings (Language and Brand Voice), plus the X actions in the inbox. | X has no verification model, so a grant is the only way in for a Member. |
| + Messages | Sending messages as a channel's own agent from Ask AI: a post into a Telegram group or a Discord channel, a private message to one member, and deleting a message Ask AI sent. | Verification never confers it, so even a verified admin needs the grant or a governance level. It is not agent configuration or moderation. |
| + Knowledge | Managing the workspace's Knowledge Base: sources, articles and Q&A, collections, reviews, Gaps, Knowledge access, and ticket canned responses. | Knowledge is workspace-level, so verification never confers it. Every member already reads the Knowledge Base. |
To assign a grant, open Team in Settings (workspace switcher, Workspace settings), find the person, and select Manage Access. You can also include grants in an invitation. See Capability Grants, including what happens when a grant is removed.
Verification
Verification is a status on one specific Telegram group or Discord server. You earn it by proving live that you're an admin there. Nobody can assign it to you.
| Where it applies | Telegram groups and Discord servers. X accounts have no verification. |
| How you get it | Fren One asks Discord or Telegram whether you're an admin of that group or server. On Discord, an agent admin role also passes the check. |
| What it unlocks | Agent configuration and moderation for that channel, its tickets, and its moderation alerts. |
| How it decays | Your status must have been confirmed within the last 72 hours. If the agent is removed or unreachable, access pauses instead of running on stale information. Re-verifying restores it immediately. |
A pause is not a removal. You keep your governance level, your grants and every read surface; only the writes on that channel stop.
Even Owners verify
Configuring the agent or moderating a Telegram group or Discord server always requires an active verification on that channel. This includes the workspace Owner, because Discord and Telegram decide who administers a group or server, not Fren One.
- Connecting a channel verifies you in the same flow, so you usually won't notice.
- On a channel someone else connected, those pages are locked with Verify to manage. If you're an admin on the platform, verifying takes one click.
- Verification can't be handed out from the Team page. To give someone access to a Discord server, add them to an agent admin role or make them a Discord admin; they then verify themselves.
- X works differently: with no verification, X access comes from the Owner or Admin level, or the + X grant.
Channel admins
When a Telegram or Discord admin verifies on one of the workspace's channels without being invited, they join as a Channel admin rather than a Member. A channel admin:
- sees only the channels they hold a fresh verification on, everywhere: Overview, Inbox, Ask AI, Reports, Analytics, Audit Log, the Channels list and their notifications;
- configures the agent on those channels, as any verified admin does;
- gets no capability grants, and reads the knowledge base without editing it;
- doesn't see Team, the workspace's settings or Integrations.
A notice on every workspace page tells them so, with Request wider access. That sends an access request; approving it gives them a seat as a Member. The Owner or an Admin can also select Make workspace member on their row in Team. An invitation, a grant, or promotion to Admin gives them a seat too. Nothing turns a seat back into a channel admin.
Example
A Member holds + Tickets, is verified on two Telegram groups, and is not verified on the workspace's Discord server. They can work every ticket in the workspace, configure the agent in those two Telegram groups, and view the Discord server's analytics without changing any of its settings.
Next steps
- Joining a Workspace: invitations, approved domains, requesting access, and channel admins
- Who Can Do What: the full capability matrix
- Capability Grants: the + Tickets, + X, + Messages and + Knowledge grants in detail
- Alerts & Notifications: why you're only told about what you can see
- Channel Lifecycle: the states a channel can be in
- Ownership & Teams: transferring ownership, the Team page, leaving a workspace