What teammates can see

There is one rule, and everything else follows from it:

Messages stay with the account. CRM data stays with the chat.

Private to the account


Messages and inbox	Only seats that have signed into that Telegram account
Own proxy, unique IP	Per account, never shared

A teammate who has not signed into an account cannot read its messages — not through the table, not through search, not through analytics. In workspace analytics, chats belonging to another seat appear as Private · {owner} with “Only the owning seat can open this chat’s analytics.”

Shared with the workspace


Custom columns and fields	On the chat
Tickets and notes	On the chat
Comments and files	On the chat
Saved views (when shared), templates (when shared)	Workspace-level

The worked example

Anna and Marco each have their own Telegram account, plus a shared @support login — one account, connected in both seats.

Chat arrives on	Who sees the chat	Who sees its CRM data
`@support` (shared)	Anna and Marco	Both — same fields, tickets and notes
Anna’s own account	Anna only	Anna only
Marco’s own account	Marco only	Marco only

Sharing an account means signing the same login into another seat. Nothing is copied or forwarded.

What the owner can additionally control

On top of the structural boundaries, the owner has explicit toggles (full list):

Toggle	Effect on members
Members can see all analytics	Off → members see only their own analytics and custom fields
Members can edit and delete messages	Off → members can’t edit or delete Telegram messages
Hide Telegram login chat from members	On → members can’t see Telegram’s service chat (777000) on any workspace account
Members can manage excluded chats	Off → only the owner can exclude or restore chats
Members can export their data	Off → only owners and admins can export
Share broadcast templates	Off → templates are personal per member
Members can create / edit / delete tickets	Individually switchable

Per-member permissions add another layer: Allow edit columns, View group members info, View group management info.

Attribution on shared accounts

When several people answer from one account, turn on Show “Sent by” badges on messages. Outgoing messages then carry the name of the member who sent them, and the Last Message Agent column shows the same in the table.

Every action is also recorded per member in Log history — messages sent, edited and deleted, field changes, ticket activity, comments and files.

Common questions

Can my boss read my DMs? Not through Entergram, unless they have signed into that same Telegram account. Messages are scoped to the account.

Can a teammate see the notes I wrote on a chat? If they can reach that chat, yes — CRM data follows the chat. If you need a private note, it doesn’t belong on a shared chat.

Can a member see login codes for a shared account? Not if Hide Telegram login chat from members is on. Turn it on before sharing accounts.

How do I keep a conversation out of all of this? Exclude it. Excluded chats leave your chat list, analytics and contact syncing. Exclusions are per user — teammates on the same shared account exclude theirs separately.

Can I stop a member deleting messages on a shared account? Yes — turn off Members can edit and delete messages. Owners and admins keep access.