Developer documentation

Telegram moderation, permissions and admin logs

Understand admin capabilities, member restrictions, role labels and native antispam with auditable moderation.

GetTGAPI editorial teamUpdated
Documentation notesReviewed

Based on official sources and independently maintained by GetTGAPI. Documentation and glossary →

On this page
  1. Check permission for each action
  2. Role labels are descriptive
  3. Keep moderation evidence
  4. Product recommendations

Check permission for each action

Admin capabilities, individual restrictions and default member restrictions use different structures and methods. Basic groups do not offer the same granular controls as supergroups. An “admin” badge is not authorization for every action.

Role labels are descriptive

Member ranks and administrator labels have specific display and editing rules. Their text is not a permission credential; enforce actual capabilities separately.

Keep moderation evidence

channels.getAdminLog supports recent activity filtering. Native antispam eligibility comes from configuration, and mistaken deletions have a dedicated reporting flow. A success toast is not an audit trail.

Product recommendations

Record the target, scope, expiry and operator of each restriction. Update badges only after confirmation and reconcile expired restrictions. A support product’s local mute or block does not automatically modify Telegram’s official account blocklist. Customer notices should explain the actual scope.