In this article
Two decisions shape everything about a room you create: whether people can talk back, and whether strangers can find it. Neither is permanent, and both are usually made without being thought about.
The second one has a consequence people discover late — a public room is readable by anyone with the address, app or no app, forever.
What you will be able to do after this step
- check_circle Choose between a group and a channel by what you want from members.
- check_circle Say exactly what going public exposes, and what it does not.
- check_circle Put a door on an invite link without making joining unpleasant.
- check_circle Explain what content protection genuinely prevents.
groups First decision: do you want to hear back?
A channel broadcasts. Only admins post, everybody else reads, and the subscriber count can grow without limit. A group is a conversation: everybody can write, and it holds a very large but finite number of people.
The instinct is to choose by size, and that is the wrong axis. The question is whether you want what members say to appear in the room. A channel can never become a conversation — you can attach a discussion group to it, but the channel itself stays one-way. A group, by contrast, can be made quiet later: permissions can restrict who posts, right down to something that functions like a channel.
That asymmetry gives a simple rule. If you are unsure, a group is the more recoverable choice. If you are certain you are publishing rather than talking, a channel is cleaner and its comment threads give you the conversation in a place that does not drown the announcements.
Second decision: public or private
This is the one with the long tail. It changes who can find the room and who can read it.
public Public
lock Private
Private unless you are trying to be found. Going public is publishing, and everything already in the room is published with it.
alternate_email What the public address actually costs
A public handle behaves like the ones in Step 009: it is claimed, it is readable, and it can be changed — at which point the old one is released and anybody may take it, along with every link that pointed at it.
Handles are limited per account on a free plan, which is the practical constraint on how many public rooms one person can run. More importantly, they are permanent in the way a domain is: put a year, a version or a season in one and you will be stuck with it or forced into a migration that breaks links.
The part that surprises people is the reading. A public room is visible in an ordinary browser, so a link you send to one person is a link anyone can open, and search engines can index what is in it. That is exactly right for a publication and exactly wrong for a working group that happened to be set to public when it was made.
Switching a room from public to private closes all of that, and releases the handle. Switching the other way does not quietly publish only future messages — it publishes the room, including what is already in it. Read the history before you flip that switch.
rule The controls on a private link
A private room's invite link is not one thing. It is a set of links you create, each with its own conditions, and using them properly removes most of the reasons people end up with rooms full of strangers.
| Control | What it is for | Worth knowing |
|---|---|---|
| Several links at once | One per place you post it, so you can see where people came from. | Also lets you kill one source without disturbing the others. |
| Expiry and usage limits | A link for an event, a cohort, a single person. | The default link has neither, which is how one link ends up circulating for years. |
| Approval required | Everybody who clicks waits in a queue until an admin admits them. | You see their name, photo and how long the account has existed before deciding. |
| Revoking a link | Stops that link working from now on. | Nobody is removed. Everyone who already joined stays, which is usually what you want. |
Approval is the control worth switching on early. Its cost is real — somebody clicks and then waits, and a queue nobody checks is worse than no queue at all, since those people are standing outside a door they think is broken. But it is the difference between a link leaking and a room filling.
shield Hiding members, and the limits of content protection
Two further switches come up constantly, and one of them is widely misunderstood.
Hiding the member list is available once a group is reasonably large. With it on, ordinary members see admins and themselves rather than the full roster. This is genuinely useful: in a public group, the member list is a contact list, and it is the reason people receive unsolicited messages the day after joining something. It is not complete concealment — anybody who writes a message is visible — but it makes harvesting the room expensive instead of trivial.
Restricting saving of content prevents members from forwarding, copying and downloading from the room. Inside Telegram it works. Outside Telegram it does not, and this is the part to be clear about: screenshot blocking depends on the platform and is not guaranteed, and a second phone pointed at the screen defeats every version of it. What you are buying is friction against casual copying, not a wall.
It also has a cost your members pay. They cannot save the thing they came for, quote it to ask a question, or forward it to the colleague who needed it — and for a channel, forwarding is the main way anything grows. If the material genuinely cannot be allowed out, the answer is a smaller audience rather than a stronger setting.
touch_app Try it now — five minutes
Four checks on a room you already run. Each one reveals something most owners have never looked at.
- Open your public room's address in a private browser window No account, no app. Read what a stranger reads. If anything there surprises you, that is the finding — and the fix is either the history or the setting.
- Look at how many invite links exist Most rooms have exactly one, created years ago, with no expiry and no limit, posted somewhere nobody remembers. Make a fresh one per destination and revoke the old one; nobody is removed.
- Turn on approval for a week Then read the queue. The account ages alone will tell you whether your link is circulating somewhere you did not intend.
- Decide the history setting deliberately Whether new members see what came before is a real editorial choice, and almost every group has whatever it defaulted to. Pick the one that matches what the room is for.
help Common questions at this stage
Can I switch between public and private later?
Yes, in both directions and at any time. Going private removes the room from search, closes web access and releases the handle for someone else to claim. Going public exposes the room and its existing history. The switch itself is instant; the consequences are not reversible in the sense that matters, because anything read while it was public was read.
What do new members see of the conversation before they joined?
In a group you choose: the whole history, or only what is said after they arrive. It is worth deciding deliberately rather than inheriting a default — a support group usually wants the history hidden, a project group almost always wants it visible so that new people can catch up without asking. In a channel, everything published is visible to any subscriber, which is the point of a channel.
If I revoke an invite link, does everybody who used it get removed?
No. Revoking breaks future use of that link and nothing else — existing members are untouched. That makes revocation cheap and worth doing whenever a link has been somewhere you did not intend. If you actually need somebody out, that is a removal, and it is a separate action.
Is there a way for admins not to be visible as themselves?
An admin can be set to post under the room's identity rather than their own name, which keeps moderation decisions from becoming personal. Two caveats: it is not anonymity from the owner, who can see who did what in the group's action log, and it has a social cost — members cannot tell whether one person or five are speaking, and have nobody to ask. The arrangement that works is usually enforcement anonymously, conversation as yourself.
How big can these actually get?
A channel's subscriber count is effectively unbounded; a group has a large ceiling in the hundreds of thousands. In practice the limit you hit first is not a number but a mode of use — a conversation stops being a conversation long before the member cap, which is what topics in Step 057 and the operations covered in Step 070 exist to address.
Which should I make if I am not sure yet?
A private group. It is the most recoverable state: you can open it up, quieten it down, add a handle, or attach structure later, and nothing you said in the meantime was published. The combinations that cause trouble are the ones where something became visible before anybody decided it should be — and that is almost always a room that was created public by default and used as though it were not.
At a glance
- 1Group or channel
A group is for talking back; a channel is for broadcasting.
- 2Going public
A public address makes the whole history readable in a browser.
- 3Private links
Invite links can expire, cap members or need approval; revoking one removes no one.
Updated
