TurnShift December update: slack topics, pricing, privacy
🪄 Channel topic updates
We now update channel topics with who's on shift at the moment and if the shift is currently running. This helps people just coming to the channel understand who they can ping.
We then update the topic when the shift ends and inform who will be on shift next, super handy.
When the shift starts:
When the shift ends:
⚠️ You need to accept new Slack permissions (set topic of public channels) for this new feature to work. You can do so on your TurnShift dashboard > organization settings.
🔐 Privacy: We no more need to know about your channel names
TurnShift being a Slack application and Slack being an important part of your work, we aim at limiting our access to your Slack data.
To this goal, we updated our Slack syncing process to avoid syncing slack channel names.
Many Slack organizations are creating channels like #cust-$companyUnderNda to talk about their customers. We initially synced those channel names to provide you a channel name search and select on the schedule page.
We choose to enhance your privacy over a slightly better UI.
Here's what TurnShift accesses and sometimes caches from your Slack organization:
- user id, name, email, avatar URL; (i.e., your employees). Users from shared channels and guest users are not synced (usually not your employees)
- public channel ids
- sending messages to public channels
- updating topics on public channels
And that's it. We still can't and won't read your Slack messages
💸 Pricing
Our new pricing is as follow:
- monthly payment: €4.20 / user / month
- yearly payment: €3.50 / user / month (€42 / year). That's two months free per user.
A user is someone you added to one or multiple teams, linked to active schedules.
⛑️ Support
- You can now access our support chat (Crisp) from the main navigation ("Get support"), and we link your Crisp identity to your TurnShift account, so we know who we're talking to.
- We can now personify your account after your approval to better help you out.
🐞🔨 Bugfixes
- ✅ Lowering the number of required people for a schedule breaks the page
- ✅ Big channel lists break the page
🤓 Tech
- We moved to Tailwind v2 and Next.js 10: all good.
- We started using TypeScript
- We've added automatic integration testing using https://www.checklyhq.com/: it's awesome :)
- We now have a way to add or remove Slack permissions and letting you know about them in the Organization settings, see:
That's it for today!
Enjoy your holidays, if any, otherwise enjoy this cat gif:
