HIGHLIGHTS
This sprint, Workspaces officially went live!
Workspaces are dedicated, private areas where your organisation can centralise travel plans. Whether you’re managing travel for a department or an entire company, Workspaces allow you to customise settings according to your specific needs.
As we double down on enabling smarter corporate travel management, Workspaces will be the hub for your team’s travel needs. In the coming weeks, expect to see more corporate-focused features, like expense management and more.
8 UPDATES
This sprint, we were mostly focused on getting Workspaces ready to ship. In addition, we also completed behind-the-scenes work on expenses, which should be released next sprint.
Workspace-related updates:
- You will now be able to create a custom name for your workspace.
- We worked on the functionality to let you add new users to your workspace, edit existing user information, and delete workspace members.
- New members will receive an email notification when they have been added to a new workspace.
- There is now a dedicated page where workspace admins can edit settings, like changing the workspace name or icon.
Expense-related updates:
- In the currency picker, we added the ability to sort currencies alphabetically. You will also be able to set a total budget value for a trip.
- Similar to how we do bookings ingestions from confirmation emails, you’ll be able to forward emails with receipts or invoice PDFs. These will automatically be mapped to existing trips that have dates matching the dates of the invoice or receipt.
- We made it so that you’ll see a placeholder when no expenses have been added yet to a trip.
- As a trip admin, you’ll be able to extract all expenses for a trip.
2 BUGS
- With Workspaces, only users with the role of admin or creators are able to use Finch Assist to create a new trip. Finch Assist didn’t get the memo, and would previously let anyone create a new trip. It’s been fixed, so now only those with the proper permissions can create new trips.
- Previously, booking ingestions would sometimes be broken by workspace modifications. This has been fixed.
