Teams are definable groups that can contain various records, including contacts, sessions, events, news, vehicles, and achievements. These teams can be used to manage volunteer teams, groups of people, classes, or regions and can have other members assigned as team leaders, allowing them to manage data inside without affecting data outside of their assigned team(s). Teams can also have front-end mini-sites in the sheepApp that show information, news, events and allow your members to apply or join.

ℹ️ A note on nouns. We tend to call these dynamic groups "Teams" - and we'll reference them as "Teams" in our documentation - but you might think of them as "Groups", "Clubs", "Sections", "Chapters" or "Registers". Our config allows you to pick the noun of your choice and this will be used in future releases of the CRM.

Teams can be configured in 2 ways:

This assumes you have accessed teams via sheepSettings.

On the teams list in sheepSettings, click on the add group button located in the top right, next to the search bar.

This will bring up a sidepanel with blank fields for you to populate with the details of the new team. In this view you can set the following fields:

Enter the name of team, which will be the main reference for the team and will be visible in sheepCRM and sheepApp.

Select a category for the team, used in sheepCRM for easy searching and grouping.

Optionally, add a subcategory to further group or filter the team with other existing teams.

Enter the main body of information about the team, visible to members in the sheepApp. This field supports basic markdown to add basic elements such as subheadings, links, bullet point lists and tables.

To act as a summary of the description, enter a single sentence without markdown which will be used in listings or search results in the sheepApp.

Optionally enter a short call-to-action to encourage members to join the team. This should either promote the team or provide details for people to contact if you wish to handle team applications outside of sheepCRM.

Once the team has been created, you will be able to upload a primary image and multiple secondary images to help visualise and promote the team. When the new team has been saved, click on the team again to edit and add images.
​
Recommended size for primary image: 800x450px or another 16:9 ratio image.
​jpeg/png file types supported
​
This will display to the right of your published content page and may be used as the page thumbnail elsewhere in the sheepApp.
​
Please click on the image below and then save it, you can then add your photo/text on top as a template.

There are additional fields that may not be relevant to your use of teams, but can be useful for handling more advanced elements of teams when using the sheepApp:

Set a minimum number of members to be in the team - this is not a hard requirement or restriction, but can be used as a guide for team leaders when managing members.

Set a maximum number of members to be in the team - this is not a hard requirement or restriction, but can be used as a guide for team leaders when managing members.

Please note that in order to add a staff member as a team leader, they must have an active sheepCRM user account with the correct user group assigned and have a record in your flock with the same email address. For more information on this process, please see this article on adding new team leaders.

If you wish to have staff members with non-admin permissions managing the team on your behalf, enter their name into this field and select their record as it appears in the dropdown list.

If using the sheepApp to handle applications for the team, you can set the team to only be accessible if the member enters an invite code. If set to yes you can enter an Invite Code which can be passed on to 'approved' members to enter in the sheepApp and start the application process.

If using the sheepApp to handle applications for the team, you can set how members can apply to join the team, with the following options:

If set to yes, only logged in sheepApp users with active memberships will be able to access and view the team in the sheepApp. Guests or non-members will be asked to log in and become a member to continue.

Optionally, enter a small paragraph of markdown supported text to explain the joining process for members. This can outline the approval process or simply list the contact details for potential applicants.

Lastly, location information can be added to the team which can be very useful for teams that are region or local specific:

A single plain text field and image can be used to show the location of the club. This can be used for a more casual description of the location, for example the name of where the team members regularly meet up or a more general region or county for the team. If an image is uploaded, this will appear instead of a dynamic map which will mark the location of the team based on the address - if entered below.

If applicable, enter the full address of the team, including postcode and country. This could be the main location of the team or team leader, or the location of a regular meet-up point.

An existing team can be used as a base or template for new teams by clicking on the duplicate icon next to the team in the teams list. This will create a copy of the team with the name prefixed by "Copy of..." - click on this new team to edit and change as needed.

From the teams list in sheepSettings, click on the team or the edit icon to bring up the configuration sidepanel. This can also be done by clicking on the configure cog icon from Alpine teams.

In the sidepanel, all fields relating to the team can be changed as needed. For more information on the fields available, please see Adding a new team above.

From the teams list in sheepSettings, click on the team or the edit icon to bring up the configuration sidepanel. This can also be done by clicking on the configure cog icon from Alpine teams.

In the footer of the sidepanel, the option to delete the team will be available. Click on delete and then click on yes to confirm the deletion.

Please note that this process can not be undone and the team can not be recovered.