Add Soor to your Telegram group
Start from the bot link, add it to the group you manage, and keep the first setup in a low-risk group when possible.
Setup guide
Set up Soor Telegram in a low-risk group first.
Use this checklist to add Soor, grant the permissions it needs, choose Normal/default live scanning or controlled private pre-scan, and review the selected setup before using it in a live community.
Admin checklist
Recommended setup order.
Promote Soor as an admin
Moderation features need admin permissions. Without them, Soor may see a problem but be unable to delete or restrict content.
Grant required permissions
Give Soor permission to delete messages. Grant restrict-user permissions where moderation actions are enabled. Soor also needs access to messages Telegram delivers according to the group, admin, and bot privacy setup.
Open the admin commands
Use /settings, /panel, /permissions, and /subscription to review the group configuration, available controls, bot permissions, quota, and plan state.
Choose the moderation posture
Use Normal/default live scanning when members should post normally. Use controlled private pre-scan when supported links and media should be submitted privately before appearing in the group.
Review the selected setup
After setup, review permissions inside Soor's panel and confirm the selected mode fits the group.
بعد الإعداد، راجع الصلاحيات من داخل لوحة سور وتأكد أن الوضع المختار يناسب المجموعة.
Move gradually to a live group
After review, apply the same settings to your live group and have admins watch early behavior for false positives, false negatives, permission gaps, and quota issues.
Mode choice
Normal live scanning vs controlled private pre-scan.
Normal/default live scanning
Members post normally. Soor scans supported content delivered to the bot. This is the lower-friction posture for communities that want moderation help without requiring private review for every controlled item.
Controlled private pre-scan
Supported links and media are deleted when posted directly. The sender is asked to send the same item privately. Approved content gets a short-lived exact-match allowance for the same user, group, and content identity or fingerprint.
Troubleshooting
Common setup issues.
Bot cannot DM the user
Controlled private pre-scan depends on private chat. If Telegram blocks the DM path, ask the user to start the bot privately and retry.
Missing delete permission
If Soor cannot delete direct submissions in controlled private pre-scan, recheck admin status and delete-message permission in the Telegram group.
Telegram privacy behavior
Telegram controls what messages and media a bot receives. Group settings, bot privacy mode, admin status, and platform behavior can affect scanning.
Quota exhausted
The Free plan includes 10 unsafe-media scans per Telegram group per day. Use /subscription to check plan and quota state.
Unexpected deletion
In controlled private pre-scan, wrong user, wrong group, wrong content, expired approvals, and reused approvals are expected to be deleted and sent back to review.
Scanner uncertainty
No scanner is perfect. Admins should review reports and tune group settings instead of treating any automated result as final.
Before launch