For the usecase I see these to be useful, I don't see lack of e2e such a huge concern. I would assume that in most cases the server would be more or less trusted in the context they are used in, so TLS style client-server security would be adequate.
In other words, if I really wanted to have discussion secret enough to warrant e2e I probably wouldn't be using company/project chat for that no matter what sort of promises it gives.
That being said, of course e2e chat would be beneficial addition, and might help especially in larger enterprise deployments.
For less important things, I agree, run of the mill TLS is enough. But for things that are critical to the business, trade secrets, strategy, SWOT analysis of a recent breach, etc, I think every company should have an e2ee chat/file sharing app in their toolkit.
>if I really wanted to have discussion secret enough to warrant e2e I probably wouldn't be using company/project chat for that no matter what sort of promises it gives.
Why not, though? Assuming logging is disabled by both parties and the E2E is working as intended, you have something that's almost as secure as in-person conversation. The only weakness is if someone has malware actively on their machine recording the conversation as it's occurring... but then you also have many other issues.
In other words, if I really wanted to have discussion secret enough to warrant e2e I probably wouldn't be using company/project chat for that no matter what sort of promises it gives.
That being said, of course e2e chat would be beneficial addition, and might help especially in larger enterprise deployments.