Group Limiting vs. Publishing Directly to Groups
There are a benefits to each method, and caveats to consider.
If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.
What is Group Limiting?
Benefits to Group-Limiting:
- You are not limited to the number of groups that can view this content using this method of limiting access—you can add as many groups as you'd like. Pro tip—If you're adding so many groups that everyone in your org can see the content, then you might not need any group limits on that content at all!
- Since you're not limited on groups that you can limit access to, you're ensuring you're publishing your content in one place, which makes modification and organization much more streamlined. Publishing directly to groups (which we'll dive into below) requires publishing to each individual group, making modification and organization more difficult to keep track of.
- If you have multiple files & folders that are group-limited and your environment has multiple groups of users accessing the same device, group limiting ensures that the content still lives on the device (albeit hidden if you're not in the group it's limited to) and it'll display or hide the content based on who's logged in at that point in time. You don't want your crew to see content intended for your managers if it's sensitive or irrelevant to them. This also means your device won't have to sync down the new content for the new user when they log in.
What is Publishing Directly to Groups?
When to consider publishing directly to a group:
- If content is only relevant to a single group, and doesn't need much modification
- If you're okay with content syncing down only once a member of a particular group logs into the app on a particular device
- From a storage-perspective, if you only need certain devices for certain groups and there isn't much cross-over, this can potentially help save on storage space.
On this page