v3.2.0

What's Changed

We've added support for the Collecting module so that items generated by the visitors will be added to the appropriate teams based on the site's team membership. Thanks @tatipovo for the report.
We've also cleaned up the REST API so that it provides appropriate messages and removed some legacy artifacts. For the REST API you can now:

• query team_resources by team to see all of the team's resource or by resource id to see all of the teams where the resource is a member. Note: Because Team Resources are essentially a join table, they don't have incremented ids (they have a composite id of the team_id and resource_id). As such, there is no way to use the REST API to find a specific team resource.
• Query team Get a more detailed picture of what assets, resource, sites and users belong to the team. Depending on the size of your site, this might be an expensive call.

This also fixes an issue where team assets weren't added to teams through the Add Team or Edit Team forms. Thanks @mquantin for the report.

See a summary of the issues address.

• Issue 94 by @alexdryden in #95
• Add collecting to teams based on associated site's teams by @alexdryden in #96
• Handle cases when user has no team and selects "Change Team" by @alexdryden in #98
• Makes the fix for list-of-sites reachable by moving REST catch by @alexdryden in #99
• Issue 100 by @alexdryden in #101
• Don't show site options on edit form by @alexdryden in #102
• Correct count on form field @alexdryden in #103
• Authority plugin refactoring by @alexdryden in #106
• Get user assets for update and create by @alexdryden in #111
• Api cleanup by @alexdryden in #113

Full Changelog: v2.1.2...v3.2.0