This is a quick one.
This week we fixed a series of weird bugs that were affecting some customers (eg. posts weren't always marked as viewed once opened) and improved the provisioning system that creates new workspaces at the end of the sign-up process.
Starting today, new workspaces will be fully configured in a matter of seconds instead of minutes.
If you're wondering why it took so long to create an account, the answer lies in our great care and attention to security and customer data. Every Pulse workspace (e.g. acme.pulse.so) is segregated and uses a dedicated AWS instance account to store all your team's data ( from usernames, passwords, emails, SAML/SSO data, to imported data from third-party APIs, etc), assets (including text posts, images, videos, files attached, etc), and other kinds of metadata.
AWS and the unique multi-account infrastructure we give our customers can support complex and enterprise-grade user management configurations (eg. setup custom SSO identity providers, custom SCIM configurations, etc) with incredibly high-security standards.
This makes Pulse both easy to use and enterprise-ready from day 0.
On a side note here are other things we fixed this week:
- Some 404 redirect bugs (shout out to James for pointing that out)
- Improved invite email onboarding experience