This feature is only available for Beta test users.
Available with Beta v153.7.
This new feature extends the existing options for controlling data and file transmission in conversations and bubbles by also enabling control over file reception. This function can be configured through profiles that are assignable to all users or specific user groups, allowing administrators to enforce data security policies with greater precision and flexibility.
Principle
A new Profile setting called Receive files is introduced and can be set to following values: Allowed, Not allowed and Company internal only.
Peer-to-peer conversation
In a peer-to-peer conversation, if the recipient has file reception disabled (set to Not allowed), the sender will either be notified that file sharing is not permitted with this user, or the option to send files will not be presented at all.
Same applies when the sender is from another company and the recipient has the option Company internal only.
But note that if the sender is in the same company, the file sharing will be allowed in this case.
- Information message
- No sharing options
Bubble conversation
The restriction on receiving files within a bubble is inherited from the permissions of the original bubble owner. Even if ownership of the bubble is transferred, the file reception rights remain based on the original creator's configuration.
- Buble inherited permissions for Receive file is Not allowed
Any invited member in this bubble will not be able to share files within this bubble.
- Buble inherited permissions for Receive file is Company internal only
Same as previous behavior applies when the invited members in this bubble are from another company, they will not be able to share files. But members of the same company as the bubble owner will be able to send/receive shared files in this bubble.
Note: The ability to read a file in a bubble is determined by the user's Receive file setting, not by the Receiving file setting for the bubble (which is inherit from the Bubble creator/owner).