Stripe Improvements π΅
[New] Team Billing Details: Team's now have more control over who owns a team's billing, invoice recipients, and the contact information that appear on invoices. To manage this information, visit the Manage Team Billing page where you'll notice a new Billing Details section.
[Updated] Customer Names in Stripe: Previously, when a new subscription was purchased only the email of the purchasing user was initially collected in Stripe. Now, when a user makes a purchase their name will also be collected.
Tool Permission Updates βοΈ
[Updated] Team Activity is a Pro Feature: We've updated the Team Activity tool to be a IMPACT+ Pro specific feature. To access this tool, users will need an IMPACT+ Pro subscription.
[Updated] Tasks Tool Permissions: We've updated the user permission's within the task tool to allow any member with an IMPACT+ Pro account to edit, delete, and complete any task on their team. This will make it easier for the team as a whole to manage a task regardless of who created initially it
UX Enhancements π
We're on a mission to build the best experience possible for our members. To this end, we push UX Enhancements every single release. If you have feedback or ideas, we would love to hear from you. You can share a feature request here or share feedback and questions in our #impact-plus-feedback channel to have a voice in the IMPACT+ product roadmap! π€―
[New] Team Coaches Have Full Pro Access: If a member on a team is set as the Coach for that team they will now have full access to all of the IMPACT+ Pro features without needing to purchase a subscription.
Bug Fixes πͺ²
In our continued effort to make IMPACT+ a more reliable platform, every release we put extra focus on eliminating key bugs in the platform! π« π¦ Here's a quick rundown on some of the top fixes:
Tools:
[Fixed] Tooltips have inconsistent UI between tools
Masterminds:
[Fixed] Private Mastermind groups are not displaying on the main Mastermind page
[Fixed] Meetings scheduled in the Mastermind groups download an ICS file instead of using AddEvent
Events:
[Fixed] Setting a featured event with another event already set as the featured results in a 500 error