Associating Buckets and Organization Units with Collaboration Groups

Administrators can associate users, buckets, and organization units directly to collaboration groups. You can use this feature to include everyone in a selected bucket or org unit, such as mobile workers, dispatchers, managers, and administrators in the associated collaboration group. Membership updates dynamically as users are added to or removed from the corresponding bucket or org unit, removing the need for manual updates.

Dynamic Group Membership

Collaboration group membership is automatically managed based on users’ association with specific buckets or organization

When a user is added to a bucket or org unit that is linked to a collaboration group, that user is automatically included as a member of the relevant group.
Conversely, if a user is removed from the bucket or org unit, they are also removed from the collaboration group. This ensures that group membership always accurately reflects the organizational structure and saves you time managing group lists manually.

Viewing Inherited Group Associations

When you access resources (such as documents or projects) that reside under buckets or org units tied to collaboration groups, you can see which groups have access to that resource:

The collaboration groups shown include both those directly associated with the resource and those inherited through parent buckets or org units.
Inherited group associations are clearly indicated in the resource’s collaboration group list, helping you quickly identify all relevant group memberships.

Editing Collaboration Groups

Editing a collaboration group presents a clear distinction between group members who joined via inherited association (through their parent bucket/org unit) and those who were added directly:

When viewing or editing the membership list, inherited members are shown separately from directly assigned members.
This makes it easy to understand how users have gained their access and to manage memberships accordingly.
You can add or remove directly assigned users as needed, but inherited users must be managed by updating their bucket or org unit membership.

Viewing All Collaboration Groups

If you are working with a resource or a collaboration group and not all possible group associations are visible, you can view a complete list:

Click the Show All button to display every collaboration group related to the resource or user.
This ensures you have full visibility of all relevant groups for effective management and troubleshooting.

Direct and Inherited Membership

A single user can be a member of a collaboration group in two ways:

By being directly assigned to the group, or
By belonging to a bucket or org unit that is itself linked to the collaboration group (inherited membership).

If a user is assigned using both methods, they will still appear only once in the group member list, but their membership method will be indicated.

This dual assignment flexibility is useful for granting temporary or special access without altering organizational structure.

Example Scenario

If your company organizes field teams by geographic regions such as East Coast, associating the East Coast organizational unit with a collaboration group such as, EC Dispatch automatically includes all users from that unit in the group. As team members shift due to transfers, hiring, or restructuring, the group membership remains accurate without requiring manual updates.

Points to remember

For frequently changing bucket structures, associate buckets with collaboration groups instead of managing individual user group assignments.
Always review inherited collaboration groups when editing user settings to avoid redundant or conflicting assignments.
This functionality is available only through the user interface. API operations do not yet support bucket/org unit-based assignments.