Telegram member permissions: defaults, exceptions and safe recovery
Design a useful posting policy, separate group defaults from individual restrictions and bot filters, then test ordinary-member access and restore settings safely.
A moderator “disables links,” but website addresses still appear. Someone is unmuted, yet cannot upload a screenshot. The owner tests a posting restriction and can still send everything. These are not necessarily broken settings: previews, group defaults, individual restrictions and exemptions answer different questions.
Start with the useful conversation you want to preserve. Choose the smallest restriction that serves that purpose, record the old values and test the return journey before applying a temporary measure widely.
Identify the layer you mean to change
| Your question | The relevant control | A useful check |
|---|---|---|
| What may ordinary members send? | Native Telegram group permissions | Text and each necessary attachment type |
| What is one person prevented from doing? | Individual Telegram restrictions; supported moderation commands | Target, duration and restoration |
| Which submitted messages should be removed? | The selected group's Defendy filters | An allowed and a prohibited example |
| Who may ask Defendy to moderate? | Defendy roles | A permitted command and an out-of-role refusal |
| Who may administer the Telegram group? | Native administrator rights | Only the rights needed for the job |
Telegram distinguishes default rights from restrictions for individual users. Granular individual restrictions are a supergroup capability; basic groups have a narrower model. Client labels and menu layouts may differ. Telegram's permission model
For granting authority to a person or a bot, use the separate administrator permissions guide. This article is about the participation policy experienced by everyone else.
Design the normal state before the emergency state
Consider a hypothetical repair community. Members need text, fault photographs and sometimes a short video. Disabling all media would also remove their main way to explain the problem. A better first question is which format causes disruption and whether a narrower restriction would leave troubleshooting intact.
In a hypothetical reading group, long voice messages may be difficult to skim or search. The team could agree on text replies while retaining photographs and source links. That is a community decision, not a ready-made Defendy preset.
Telegram's native permission families cover messages, photos and videos, files, audio and voice messages, polls, stickers and animations, along with invitations and some group-management actions. Use the controls actually shown for your chat and client; a feature in another bot's panel is not evidence of a Defendy setting. Telegram's member-rights reference
Before switching something off, answer four questions:
- Which useful activity requires this format?
- What observed problem are we trying to stop?
- Would a clear rule or one person's temporary restriction be enough?
- Who will verify that normal participation still works?
Avoid a “deny everything just in case” baseline. A restriction needs both a purpose and a condition for reconsidering it.
Link previews are not link text
A preview is the page card attached to a message. Controlling previews does not create a domain policy. If messages containing particular links should be removed, configure Defendy's link filter separately.
This also explains an important diagnostic distinction. A native permission can prevent an action; a message filter acts on a message that has arrived. “I cannot send it” and “it appeared and then disappeared” point to different checks. If several bots operate in the group, establish which one acted.
Allowing a domain does not certify every page on it, and turning previews off does not turn link filtering off. Telegram's ChatPermissions reference
Change permissions without losing your starting point
- Record the baseline. Open the intended group's information, editing controls and permissions. Note the current values, date and known individual exceptions. A screenshot can help if it avoids unnecessary personal information.
- State the purpose. For example: keep image-based troubleshooting available while stopping a stream of voice messages. Tell members what is changing and where to ask for help.
- Change one coherent set of controls. Reopen the settings after saving. Changing permissions, CAPTCHA and multiple filters together makes failures difficult to attribute.
- Test with an ordinary member. Try text, a useful attachment and the format you intended to restrict. Test content filters with separate allowed and prohibited examples.
- Assign restoration. For a temporary measure, record who will review it, when and which exact values should return. Do not assume a group-wide permission change has an automatic rollback.
In Defendy's Mini App, verify the selected group before adjusting modules. Similar names are easy to confuse. A saved filter setting and a native Telegram permission are separate things to check.
Why your administrator account is a bad test
Telegram's member permission object concerns non-administrators. Groups may also have boost-based exemptions. Do not use an account with an applicable exemption to represent an ordinary participant. Telegram's group information
Defendy adds another distinction. Its reviewed message pipeline skips Telegram administrators before automatic filtering. Within Defendy's own role matrix, Exempt member, Co-founder and Owner have filter immunity. The internal Administrator role alone does not include that immunity, although the same person may also be a native Telegram administrator.
Use a consenting regular member without Telegram administration, boost-based privileges, individual exceptions that alter the test, or Defendy filter immunity. Do not remove essential authority from the owner just to experiment; use a separate test group and an appropriate account. The role matrix explains the product roles.
Filter immunity does not grant native posting rights, nor does it create a configurable CAPTCHA exemption. Promoting a member or assigning /free is not a general-purpose access repair.
Test an individual restriction in both directions
If one member is causing the problem, changing everyone's posting rights usually affects too many people. Defendy supports a timed mute with /tmute. In a test group, an authorized moderator can reply to a consenting member's harmless message with /tmute 2m permission test.
Check three states: they can post beforehand, cannot post during the restriction and can post again when it ends. Separately test early removal with /unmute. This is a posting restriction, not a Mini App editor for that person's individual media permissions.
The recovery owner matters. Defendy's Junior moderator role can mute, but unmuting requires at least Moderator. Arrange access to someone who can reverse a mistake before giving a new volunteer their first shift. The bot also needs the appropriate native Telegram rights. Moderation commands
If the aim is to restrict only one format for one person, inspect Telegram's native individual controls. Do not substitute an indefinite full mute or assume Defendy exposes a granular custom-permission editor.
Access still looks wrong after restoration
Work from the broadest scope toward the specific account:
- Does it affect other regular members? Compare group defaults with the recorded baseline. Removing one person's restriction is not a group-settings rollback.
- Does it affect only this person? Inspect their current restrictions, duration and individual exceptions. Confirm that the command targeted the correct account.
- Does it affect a newcomer? Check CAPTCHA completion and the actual joining route. The current Mini App has no separate first-N-hours silence editor or role-based CAPTCHA exemption editor. See CAPTCHA setup.
- Do messages disappear after being sent? Review the relevant filter and selected log events. Another rule may be acting again rather than the old mute remaining in place.
- Was the person banned or removed? Unbanning does not automatically bring them back; they need an available way to rejoin. That is a different recovery path from unmuting. Telegram's unban behavior
When reopening a group, restore the recorded values rather than enabling every switch. Recheck people with individual restrictions separately. This avoids turning a temporary defense into either a permanent restriction or an unintended permission expansion.
Keep a compact permission-change note
Record the group, reason, old values, new values, regular test participant, observed posting behavior, restoration owner and result of the final test. This is a suggested team note, not a claim that Defendy automatically records every configuration change.
If the observed state still differs from the settings, use the access recovery guide. Establish which layer is responsible before giving anyone more authority.
Sources and review boundary
Reviewed on 5 October 2026 using the linked primary Telegram references, Defendy's current role and message-filtering implementation, and its command documentation. Community examples are hypothetical. The procedures are proposed checks, not reports of a live production test.
