Teams
Teams helps WinnerWare organize users into structured teams and use those team relationships across access control, content editing, and notifications.
Overview
This module is used when users should belong to one or more teams and WinnerWare needs to act on that structure. It supports team assignment, parent-child team hierarchies, optional content restriction by hierarchy, and a team-owner notification task for workflows.
Key Features
- Adds a reusable Teams content type.
- Supports parent-team hierarchy.
- Supports team-owner selection for a team.
- Lets administrators assign teams to users.
- Adds an optional team-based content restriction feature.
- Adds a workflow task for notifying team owners.
How It Works
The main feature introduces a team content type and the parts needed to assign teams to users or content. Teams can be arranged in a hierarchy, and the optional restriction feature uses that hierarchy to limit access to content by relationship.
The module also supports a workflow task that can notify the owners of a team when team-aware processes need to send a notification.
Configuration
| Admin display name | Feature ID | Purpose |
|---|---|---|
| Teams | CloudSolutions.Teams | Adds team structures, user assignment, and team-aware content parts. |
| Restrict Content by team hierarchy | CloudSolutions.Teams.Contents | Applies hierarchy-based content access restrictions. |
Team structures added by the module
| Item | Purpose |
|---|---|
| Teams content type | Stores the team records used across the site. |
| Parent Team | Lets a team belong under another team. |
| Coaches | Lets a team store one or more designated owners. |
| Teams user field | Lets a user be assigned to one or more teams. |
Permission
| Permission | Purpose |
|---|---|
| Edit current user team | Lets permitted roles manage the current user's team assignment. |
Usage
Use this module when WinnerWare needs formal team structure instead of loose role membership alone. It is especially useful when access, oversight, or notifications should follow a team hierarchy.
Example setup
One clear setup pattern is:
- create the Teams content items the business will use
- set a parent team where hierarchy matters
- assign the correct coaches or owners to each team
- update user team assignments so users belong to the right structure
- enable the restriction feature if content access should follow the team hierarchy
Developer Notes
- The team content type includes title, parent-team, and owner fields.
- The current implementation creates supporting indexes for teams and user-team relationships.
- Editors, moderators, and administrators receive the team-edit permission by default.
- When workflows and notifications are enabled together, the module adds a Notify Team Owners workflow task.