Who is this article for?

Administrators who manage teams

Defined responsibilities and elevated access required.

Workflow steps and tasks may be allocated to a user or a team. When notifications regarding objects are disseminated to a team, the task assumes an agile or collaborative nature, thereby informing each member of their respective requirements and responsibilities. Effective communication is essential to ensure that assignments are comprehended and executed efficiently.

Teams can have members added and deleted, but a team itself cannot be deleted. Teams that have been checked as Enabled are included in selectable team lists. Unchecking the Enabled box will hide the team from the list, however, objects assigned to a team will continue to be active and linked to the team members until such time as they are completed or reassigned.

By default, Teams are sorted by a free-text Category field, but they can be rearranged and sorted by Name.

External Party team members are non-users included in the notification distribution list to collaborate on workflow tasks. They can view information displayed on a notification but cannot access the system information without a user account.

Team members by default, will be active for one hundred years. Team members are added and removed from team notifications using the Effective From and Effective To dates.

Teams with inactive users
When a team is used for workflow assignments, the team must have at least one active user to protect workflow tasks from becoming orphaned. Advancing a workflow task assigned to a team without at least one active user will cause an error.