Configure workspace permissions and privacy

Settings → Privacy Settings, workspace privacy controls and operational defaults. Owners and admins only.

Member access settings with separate edit and delete message switches — Control editing and deletion independently. Owners and admins keep access when either switch is off.

Each toggle controls what members can do. Owners and admins keep access to everything unless stated otherwise. The header shows {n}/{total} active.

Member permissions

What members can see about your contacts, and what they can change in the workspace.

Hide Telegram contact and group details

On, members cannot see Telegram usernames, phone numbers, bios, group members, roles, invitation links or chat IDs. First and last names stay visible. Owners and admins always keep access. Only the workspace owner can change this switch.

Hide names

Appears nested under Hide Telegram contact and group details while that switch is on, and only the workspace owner can change it. It is off by default.

On, members also see every name shortened to its first 4 characters followed by ***: people, groups, supergroups and channels. A group called Partners EU shows as Part ***. Use it when even the names of the groups and channels your accounts are in are sensitive.

Members see a Names hidden badge explaining the restriction. Owners and admins still see full names.

Limit members to their own analytics

On, members only see analytics for chats on their own Telegram accounts, including custom field analytics. Owners and admins always see everything. Off, members see workspace-wide analytics.

This is the single biggest visibility switch in the product. Turn it on for teams where individual performance data shouldn’t be shared.

Members can exclude chats from the CRM

On, members can exclude chats from the workspace. Off, only the workspace owner can add or remove excluded chats. Members see “The workspace owner has locked changes to excluded chats.”

Members can edit messages and Members can delete messages

These are separate switches, both on by default. Turn either one off to prevent members from performing that action. Owners and admins retain both permissions. Workspaces that previously disabled editing and deletion keep both actions disabled.

Eligible messages still show Edit and Delete in the action menu. A workspace restriction adds a lock icon and disables the action. Hover over it on desktop, or tap it on mobile, to see Contact your administrator to enable this feature. Telegram’s own message eligibility rules continue to apply.

These restrictions also apply when message edits or deletions are requested through the Public API or MCP.

On, seat members cannot see Telegram’s service chat (777000), where login codes arrive, on any workspace account. Employees can’t sign the account in on another device or take it over. Owners and admins always keep access. Members see a Login codes hidden badge.

This is also a prerequisite for connecting a Telegram account on a member’s behalf. Without it, login codes for shared accounts would be readable by every member.

On, templates are shared across the workspace. Only the creator can edit, and attachment storage pools across seats. Off, templates are personal per member.

Restrict data exports to owners and admins

On, members cannot export data from their workspace accounts. Owners and admins can always export. Off, members can request exports of their own data. See Data export & deletion.

Tickets

Enable tickets and set what members can do with them.

Toggle	Effect when off
Enable tickets for the workspace	Tickets are hidden for all workspace members, the nav item disappears
Members can create tickets	Members can’t open new tickets
Members can edit tickets	Members can’t change status, priority, fields or linked chats
Members can delete tickets	Members can’t permanently delete tickets

Advanced

Show “Sent by” badges on messages (Experimental)

Outgoing messages show a badge with the name of the workspace member who sent them. Useful for teams sharing Telegram accounts. Feeds the Last Message Agent column.

Operations & Automation

Message Attribution

Ties outgoing messages to the member who sent them, across shared accounts.

SLA Configuration

Global SLA (hours), “Default SLA for all new and existing tickets without manual SLA override.” Shows Enabled / Disabled; supports presets or a Custom value in hours or days. See SLA.

Recommended configurations

Sales team (each rep has their own Telegram)

Setting	Value
Limit members to their own analytics	Off, coaching needs visibility
Members can edit messages	On
Members can delete messages	On
Members can exclude chats from the CRM	On
Hide Telegram login codes from members	On
Share broadcast templates	On, one message library
Restrict data exports to owners and admins	On
”Sent by” badges	Off (each rep has their own account)

Support team (shared inbox)

Setting	Value
Limit members to their own analytics	Off
Members can edit messages	Off, protect the record
Members can delete messages	Off, protect the record
Members can exclude chats from the CRM	Off
Hide Telegram login codes from members	On, required for delegated connections
Share broadcast templates	On
Restrict data exports to owners and admins	On
”Sent by” badges	On, you need to know who answered
Tickets + Global SLA	On

Agency / contractors

Setting	Value
Limit members to their own analytics	On, contractors see only their own
Members can edit messages	Off
Members can delete messages	Off
Members can exclude chats from the CRM	Off
Restrict data exports to owners and admins	On
Members can delete tickets	Off

What these toggles do not do

They control what members can do inside Entergram. They do not restrict Telegram itself - a member who has independently signed into a Telegram account can always use the Telegram app.

For the underlying data boundaries, see What teammates can see.