- CheckMates
- :
- Products
- :
- Harmony
- :
- Mobile
- :
- Deny file attachment in capsule workspace
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Deny file attachment in capsule workspace
Hi,
We're using Capsule Workspace on employees mobile phones, mainly for emails.
Is there a way to block users from attaching files from their phone when creating new emails on the app?
Thanks
- Labels:
-
Android
-
iOS
-
Management
-
Network Protection
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please review "sk109760: Capsule Workspace Document Control Feature" and see if it helps you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please review "sk109760: Capsule Workspace Document Control Feature" and see if it helps you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Chris,
Thanks for the SK.
If I understand correctly, the part in the SK that could help me is this one:
Accept protected files with these extensions from external apps | key_00150_accept_protected_extensions | Describes which extensions can "enter the boundaries" of Workspace. This holds only for Capsule Docs protected files. | Comma separated extensions (see explanation below) | $all |
Accept unprotected files with these extensions from external apps | key_00160_accept_unprotected_extensions | Describes which extensions can "enter the boundaries" of Workspace. This holds only for files not protected by Capsule Docs. | Comma separated extensions (see explanation below) | $all |
and theoreticaly just need to leave these fields blank?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks correct to me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks,
I'll give it a shot and update later
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I noticed I didn't see any uninstall instruction, in case it messes things and I want to remove it.
Do you know perhaps?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Make sure this value is set to "none"
key_00160_accept_unprotected_extensions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Chris,
I'm just now getting to this...
I don't see any roll back/uninstall instructions in the SK.
Can you advise please?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My assumption is you should capture the current/default state of those attributes and return to those if needed, if you need confirmation of this please contact TAC for an official statement.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How do I capture the current state of those attributes if they only exist after the implementation of this SK?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The SK notes the default values... $all
You can obviously also take your usual snapshot/backups if deemed necessary.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just to update I implemented according to the SK and it works great!
Thanks
