Teams

What are Teams?

In ShareDo, teams are a way of grouping together users who share a particular set of characteristics. A team does not need to be a physical ‘HR’ team (although it can be). Users can be in multiple teams, and they can change teams based on their skill level or fluctuations in workload. In the image below:

Your personal level of access within ShareDo is an accumulation of the permissions of all the teams you are a member of.

Internal Team

A team consisting of internal users of the default organisation.

External Team

A team of external users from outside the default organisation, perhaps client users.

Team Types

The team type defines how the team is used in the system and is an important part of your configuration.

Team Type	Description
ACL	An ACL team is an access control team. An ACL team is used to assign permissions to users with similar security requirements. An individual user's permissions can be controlled through the ACL teams they are a member of. Adding a user to multiple ACL teams will give them the sum of the permissions of all the teams they are a member of. ACL teams should NOT be added to matters, instructions or ShareDo types. They should only be used to assign permissions.
Department	Team type designed to manage structures of people or sub-teams typically for reporting purposes.
External Teams	External teams are used to group together external users, such as members of a client organisation. External teams can be used to give external users access to work via the external portals. Tasks can be assigned to external teams. As with internal users, the permissions for external users should be managed via an ACL team.
Pods	Pods are used for assigning work. Different pods of resources can be used to assign different difficulties or types of work. The ShareDo allocation rules and the execution engine can be used to assign the right work to the right people. Users can belong to multiple pods and can be moved between pods as workload varies or skill level changes.
Structural teams	Structural teams are used to provide a hierarchy of teams, for example, Company A > Department B > Team C You can use this team type to make your team hierarchy more understandable.

Team Details

This is some of the information you can use to describe your team. Data capture for teams can be amended using the Aspects functionality.

Team Type	Description
Name	The name displayed in your user interface for the team.
Short Name	Shortened name - can be useful for documents/references.
Parent Team	The parent team of your team in the team hierarchy.
Type	As mentioned above, there are different types of teams. Ensure your team is a POD if you want to assign work to it.
Description	Give your team a functional description to describe the purpose of the team.
Reference	The internal reference for the team.
External Reference	External reference for the team.
Location	The team's location - you may want to use this if you want to send communications from the team.
Working Day Calendar	Set the dates and times your teams work.
Contact Details	Set email and other contact details for your team here.
Contact Preferences	Enter the preferred contact details for the team.

Team Membership

Users can be members of one or more teams in the application.

Add a User to a Team

In the out-of-the-box workbench configuration, users can see work based on their teams. The team worklist provides a view of all work across all teams the user belongs to, allowing them to prioritise their entire workload.