ContributionsMost RecentMost LikesSolutionsPreparing for Automations End of Support on June 30, 2022 Workflow automation has taken many forms in Quickbase over the years. It could be a simple email notification, a dynamic form rule, or even a complex script triggered by a webhook. But one thing that’s clear is that workflow automation is only going to increase in importance for customers and use cases of all kinds. To meet those evolving requirements, we have spent the last year growing and improving the workflow automation capabilities of our powerful new Pipelines technology. Now, as we continue to look toward the future, we must also evaluate the role of older and less flexible features like Quickbase Automations. That’s why we will be retiring Quickbase Automations in favor of Pipelines. On June 30, 2022, Automations will reach End of Support. What End of Support means for you The next step in retiring Automations will come on June 30, 2022, when the feature will reach End of Support. At that time, you will no longer be able to create new automations. This also means that the Quickbase Technical Support team will not be able to assist with the Automations feature after June 30, 2022. Existing automations will continue to be editable, and they will continue to run until Automations reaches End of Life. Read on to learn about the benefits of using Pipelines instead of Automations, and how you can prepare for Automations retirement by migrating your existing automations. Improving your workflow using Pipelines We have been continuously adding new capabilities and tools that will make it easy for you to migrate your workflow automations to our newer and more powerful Pipelines technology. Not only will this ensure that you don’t experience any disruption to your business or your processes, but it also opens the door to new workflow ideas that can connect across multiple systems. Pipelines supports all Automations features – Pipelines now supports all the features you’ve been leveraging within Automations, including the ability to query the previous value of a field. Pipelines enables more sophisticated logic than Automations – Pipelines supports more powerful business logic than Automations, including branching and looping, as well as parsing text. Pipelines gives you the ability to scale workflow across systems – In addition to orchestrating workflow within your Quickbase ecosystem, Pipelines includes point-and-click integration with over 30 products including Outlook, Slack, and Sharepoint. We are committed to supporting every Automations use case. That’s why all Quickbase customers get unlimited use of Quickbase-to-Quickbase Pipelines included with their service plan at no additional cost. Focus areas for improving Pipelines We’ve gotten feedback from many of you on Pipelines, about what’s going well and where we have opportunity to improve. Thank you for taking the time to share your thoughts with us. Getting this perspective is essential to help us evolve our product and make sure we are serving this community well. There are three main areas we are focusing on to further support you as you migrate from Automations: Ease of use – We are working on improvements to make it faster and more intuitive to build pipelines. For example, in the January 2022 release we are making our builder wizard generally available. Using the wizard, the user first chooses which steps to include. Then, they are directed to the pipelines designer page where they fill in the details for how each step should work. We have also extended our Pipelines educational resources in Quickbase University, with the release of our new Pipelines Builder certification exam. Performance – In December 2021, we rolled out the new “Blaze” engine to offer better reliability, performance, and efficiency for Pipelines. Compared to November 2020, usage of our Pipelines capability has multiplied by more than 71 times, and the Blaze engine helps support that exponential increase in workload. It also lays the foundation for the next round of exponential growth in integration and automation use-cases which companies are looking to create with Quickbase Pipelines. We’ve seen pipelines run 30 times faster on average since releasing the Blaze engine. Governance – We are making major investments to make it easier to manage your pipelines at scale. Account administrators will be able to set access to Pipelines channels by individual user, or by user group. Pipelines builders will also be notified when one of their pipelines encounters an error. And finally, app builders will be able to see a list of pipelines connected to their app. Each of these features will be available in the first half of 2022, before we reach the End of Support date for Automations. Preparing to migrate There are three steps you can take to prepare for your migration from Automations to Pipelines: Make sure you have access to Pipelines – Some of you are app builders who have built automations but have not had a chance to start working with Pipelines. It’s worthwhile to check the top-left of your Quickbase view to make sure you have Pipelines access set up. If you do not see the Pipelines tab, you’ll need to contact one of your account admins to get access. Create new workflow automations using Pipelines instead of Automations – Since Automations will not be supported starting on June 30, 2022, this is the perfect time to stop creating new automations and creating pipelines instead. We have many resources available to bring you up to speed. (Check out our list on the community.) Begin migrating your existing automations to Pipelines - We’ve developed a simple migration tool you can use to create a corresponding pipeline for each of your automations, which you can do in just a few clicks. We have been improving the migration tool over the past few months, and it is now ready to migrate virtually any automation. (Learn more about using the migration tool in our help article.) Timeline Over the several months, we will be following our standard feature retirement lifecycle, and taking several steps along the way to retire the Quickbase Automations feature. Timing Retirement Phase Description June 22, 2021 End of Sale We will focus on making sure that all our customers have the information and resources they need to successfully plan for the migration of their Automations to Pipelines. Even though the Automations feature will still be available to existing customers, we encourage customers to begin using Pipelines to implement new workflow automation ideas moving forward. June 30, 2022 End of Support Your existing Automations will continue to run without interruption, but you will no longer be able to create new Automations or get assistance with the building and configuration of Automations from Quickbase staff. During this time, we encourage you to migrate any remaining Automations to Pipelines at the earliest possible opportunity. TBD End of Life Automations is officially retired. This means that it is fully removed from our product, and remaining Automations will cease to function. Learn more Learn more about using the migration tool in our help article. Take the Getting Started with Pipelines course in Quickbase University. Take the Pipelines Builder certification exam. Browse all the Pipelines resources available on the community. Explore the 30+ point-and-click integration channels available for Pipelines. Learn more about Quickbase’s process for retiring product features. Introducing New Quickbase Navigation (beta) Quickbase is the world’s first platform for dynamic work management. And that means we wake up every day asking ourselves how we can make our customers more efficient and help them grow. We are continually improving the platform and adding new capabilities, so it is easier than ever for you to see, connect, and control your most complex processes. To do that, we want to make sure we continue to focus on providing an intuitive, clean user experience, which is the foundation on which the rest of Quickbase relies. That’s why we’re excited to announce the beta version of our new navigation. Here’s what to expect from our new navigation, and how you can try it out today. What’s changing? We rebuilt Quickbase’s navigation from the ground up to provide a more modern and intuitive experience for both you and your users. And, while we have future plans to add new functionality and concepts to our navigation, we’re not adding any new elements just yet. Instead, this initial release of our new navigation will re-arrange the components you use to navigate around your apps today. This approach will ease you and your users into this experience and make it easier to manage this change. Tables have moved to the left side Some may call it clunky; others call it dated, but we heard loud and clear from many of you that the Quickbase menus at the top of the page take up too much room. That’s why we’re moving app-level links to a new sidebar which you can find at the left edge of the page. Here, you can navigate to each table in your app. And if you are an app admin, you will find links to app settings and the user management page. We’re also providing centralized access to all your table settings with Settings for each table directly in the content menu are designed to save you time and clicks. It’s important to note that your existing table order and permissions will translate 1:1 from legacy navigation to the new style, so you’ll be able to hit the ground running without the need to re-calibrate your settings. With more room to breathe, you can see – and understand - more of your own data on your screen at once. There are several ways you can choose to interact with this menu, depending on how you like to get work done. You can open the sidebar by clicking the arrow to push content and maintain your open/closed state as you navigate across pages or simply hover anywhere over the closed sidebar to open temporarily and close automatically as you navigate. Switch between apps using the new global nav menu We’re cleaning up the experience of having to switch between apps with the app bar, by moving these controls to the top-left corner of the page. In this new waffle menu, you’ll be able to switch between apps. This is also where you will access other parts of Quickbase outside of apps, such as Pipelines and Exchange, enabling one-click access to key areas of the platform. Getting involved in the beta program Want to be one of the first to get your hands on the new nav? Your valuable feedback is pivotal to shaping our platform. Register here! Next steps The new navigation will be available for all users starting on May 8, 2024, with the ability to try it defaulted on. Each account admin can choose to disable the new navigation for their users under the Admin Console-> Permissions menu. If a user’s ability to turn the new navigation is not disabled, they can visit their user preferences and select sidebar navigation to try out the new experience. Happy navigating! Re: Bringing attention to the End of Life for Webhooks Hi there, so we do not currently have any plans to retire the XML API. While the RESTful API offers more modern functionality, we understand that the XML API plays a slightly different role in Quickbase (for example, when you create a relationship, the Add Child Record button uses the XML API). Also, with our upcoming Solutions API capability, you will be able to programmatically create and manage Pipelines so that is something we are currently working on. ------------------------------ Brian Cafferelli Product Marketing Manager | Quickbase ------------------------------ Re: Bringing attention to the End of Life for Webhooks Hi Gary, I wanted to clarify that this change will not disrupt workato workflows. I will add that to the community post. ------------------------------ Brian Cafferelli Product Marketing Manager | Quickbase ------------------------------ Re: Creation of new QB Actions and Webhooks will be locked as of June 30, 2024 Also, Jim you mentioned that the process of setting up a new pipeline feels slow to you. Can you tell me know about what you're seeing? I'm curious whether you have tried out our new pipeline designer. You may also be able to accelerate the setup by importing a pipeline via YAML. Re: Creation of new QB Actions and Webhooks will be locked as of June 30, 2024 Hi everyone, thank you for the great feedback! I want to reiterate that we are exploring improvements to Pipelines to address sharing, bulk triggering, and trigger speed. From all we've heard from the community, it sounds like these are the primary concerns folks have at this point but we are definitely interested to hear about the experiences you've had with Pipelines so we can help set you up for success. Creation of new QB Actions and Webhooks will be locked as of June 30, 2024 Top of FormQBQuickbase makes it easy to reduce repetitive tasks and orchestrate workflows, uniting disconnected data onto one platform. With Pipelines, business users can manage both automations and integrations in one place. And we have been hard at work enhancing our Pipelines capability based on your feedback. Now, as we continue to look toward the future, we must also evaluate the role of older and less flexible features like Quickbase Actions and Webhooks. These two features will reach End of Sale on June 30, 2024, and creating new actions/webhooks will be locked at that time. What this change means for you Any actions and webhooks you’ve already created will continue to run, and you will still be able to edit them. However, you will no longer be able to create new actions or automations. We strongly recommend that you avoid using unsupported features such as QB Actions and Webhooks because doing so presents a risk of disrupting your team’s workflow. Instead, you should build a pipeline for each your remaining actions and webhooks. If you are an app builder, you already have access to create pipelines. If you do not see the Pipelines link below, please contact your account administrator to get access. NOTE: This change to webhooks will not impact workflows you've built in Workato that connect to Quickbase. The Pipelines Advantage We have been continuously adding new capabilities and tools that make it easy for you to transition your workflow automations to our newer and more powerful Pipelines technology. Not only will this ensure that you don’t experience any disruption to your business or your processes, but it also opens the door to new workflow ideas that can connect across multiple systems. Pipelines supports all QB Actions and Webhooks features – Pipelines supports all the features you’ve been leveraging within QB Actions and Webhooks, including the ability to query the previous value of a field. Pipelines enables more sophisticated logic than Quickbase Actions and Webhooks – Pipelines supports more powerful business logic than QB Actions and Webhooks, including branching and looping, as well as parsing text. Pipelines gives you the ability to scale workflow across systems – In addition to orchestrating workflow within your Quickbase ecosystem, Pipelines includes drag-and-drop integration with over 40 products including Outlook, Slack, and Sharepoint. Recent Pipelines Improvements We are making major improvements to Pipelines, which make it easier to build, enable more powerful pipelines, and make them easier to govern and manage. Easier to build: ImprovedPipelines Designer offers a streamlined, drag-and-drop experience Simplified setup for Quickbase channel no longer requires user tokens to be created manually More powerful and reliable pipelines: New integration channels forFastfield and Snowflake ImprovedOutlook channel enables replying to email thread ImprovedQuickbase channel enables exporting records to CSV Pipelines trigger up to 5x faster Increased limit on outbound webhooks from 20/second to 50/second Improved governance: Added pipelines to Field Usage Pipelines can be backed up easily via Solutions Connection Central now includes both Pipelines and Sync tables Static IP Addresses for Outgoing Pipelines Focus areas for improving Pipelines We’ve gotten feedback from many of you on Pipelines about what’s going well and where we have opportunity to improve. Thank you for taking the time to share your thoughts with us. Getting this perspective is essential to help us evolve our product and make sure we are serving the community well. Looking forward, we are exploring a number of Pipelines enhancements: AI-powered pipeline generation Support for official service accounts New bulk trigger step Initial trigger time improvements Connection Central improvements What’s coming next Looking further ahead, Quickbase Actions and Webhooks will reach End of Support in December 2024. At that point, existing actions and webhooks will continue to run, but you will no longer be able to edit them or create new ones. We plan to keep existing actions and webhooks running for the foreseeable future. If this changes, we will make sure to provide a reasonable amount of notice first. Our annual Empower conference is coming on May 8, 2024, where you can learn more about our upcoming plans for Pipelines as well as other exciting innovations we have coming soon. This will be a free, virtual event – sign up today! Learn more Take the Getting Started with Pipelines course in Quickbase University. Take the Pipelines Builder certification exam. Explore the 40+ no-code connectors available for Pipelines. Learn more about Quickbase’s process for retiring product features. Automations will no longer be editable as of June 30, 2024 Quickbase makes it easy to reduce repetitive tasks and orchestrate workflows, uniting disconnected data onto one platform. With Pipelines, business users can manage both automations and integrations in one place. And we have been hard at work enhancing our Pipelines capability based on your feedback. Now, as we continue to look toward the future, we must also evaluate the role of older and less flexible features like Quickbase Automations. Support for the Automations feature ended in June 2022, and editing existing automations will be locked on June 30, 2024. What this change means for you Beginning in June 2022, creating new automations was locked, however existing automations continued to run and could be edited at any time. Beginning June 30, 2024, automations you have already built will continue to run. However, you will no longer be able to edit your automations. We plan to keep existing automations running for the foreseeable future, rather than moving it to End of Life. If this changes, we will make sure to provide a reasonable amount of notice first. We strongly recommend that you avoid using unsupported features such as Automations because doing so presents a risk of disrupting your team’s workflow. Instead, you can migrate your remaining automations to pipelines. We’ve developed a simple migration tool you can use to create a corresponding pipeline for each of your automations, which you can do in just a few clicks. We have released more improvements to the migration tool recently, and it is now ready to migrate virtually any automation. (Learn more about using the migration tool in our help article.) If you are an app builder, you already have access to create pipelines. If you do not see the Pipelines link below, please contact your account administrator to get access. The Pipelines Advantage We have been continuously adding new capabilities and tools that make it easy for you to migrate your workflow automations to our newer and more powerful Pipelines technology. Not only will this ensure that you don’t experience any disruption to your business or your processes, but it also opens the door to new workflow ideas that can connect across multiple systems. Pipelines supports all Automations features – Pipelines supports all the features you’ve been leveraging within Automations, including the ability to query the previous value of a field. Pipelines enables more sophisticated logic than Automations – Pipelines supports more powerful business logic than Automations, including branching and looping, as well as parsing text. Pipelines gives you the ability to scale workflow across systems – In addition to orchestrating workflow within your Quickbase ecosystem, Pipelines includes drag-and-drop integration with over 40 products including Outlook, Slack, and Sharepoint. Recent Pipelines Improvements We are making major improvements to Pipelines, which make it easier to build, enable more powerful pipelines, and make them easier to govern and manage. Easier to build: Improved Pipelines Designer offers a streamlined, drag-and-drop experience Simplified setup for Quickbase channel no longer requires user tokens to be created manually More powerful and reliable pipelines: New integration channels forFastfield and Snowflake ImprovedOutlook channel enables replying to email thread ImprovedQuickbase channel enables exporting records to CSV Pipelines trigger up to 5x faster Increased limit on outbound webhooks from 20/second to 50/second Improved governance: Added pipelines to Field Usage Pipelines can be backed up easily via Solutions Connection Central now includes both Pipelines and Sync tables Static IP Addresses for Outgoing Pipelines Focus areas for improving Pipelines We’ve gotten feedback from many of you on Pipelines about what’s going well and where we have opportunity to improve. Thank you for taking the time to share your thoughts with us. Getting this perspective is essential to help us evolve our product and make sure we are serving the community well. Looking forward, we are exploring a number of Pipelines enhancements: AI-powered pipeline generation Support for official service accounts New bulk trigger step Initial trigger time improvements Connection Central improvements Our annual Empower conference is coming on May 8, 2024, where you can learn more about our upcoming plans for Pipelines as well as other exciting innovations we have coming soon. This will be a free, virtual event – sign up today! Learn more Learn more about using the migration tool in our help article. Take the Getting Started with Pipelines course in Quickbase University. Take the Pipelines Builder certification exam. Explore the 40+ no-code connectors available for Pipelines. Learn more about Quickbase’s process for retiring product features. The legacy exchange will be replaced on March 24th, 2024 The Quickbase Exchange gives you a head start when building a new app. It offers a range of pre-built app templates for you to explore. And if you find that one you like, you can use it as a starting point and customize it for your unique business needs. In June 2023,we released the beta version of our new exchange, which we re-built from the ground up and expanded to include a broader range of builder resources. On March 24, 2024, the new exchange will reach general availability and we will be shutting down the legacy exchange at that time. What this change means for you For your app template needs, you can now leverage our new exchange. It provides a streamlined user experience, focusing on a smaller set of templates which have been updated with all our newer UI features such as forms and dashboards. If there’s an app which is listed on the legacy exchange but not listed on the new exchange, you can make your own copy of it before March 24. Or, if you are looking for an app after March 24 that is not in the new exchange, you can open a support ticket and we can provide you with your own personal copy of the app in question. A whole new exchange The new exchange makes it easier than ever to build in Quickbase, whether you’re working on an existing app or starting a new one. Let us give you a head-start with your building now that the new exchange offers: A refreshed look-and-feel: We’ve modernized the interface to make it easier to find what you need Less clutter, faster building: The exchange now focuses on a smaller set of app templates which have been updated with new forms, dashboards, etc. Apps and app components: In addition to app templates, the new exchange also offers a range of formulas as well as jinja snippets (for pipelines). Our annual Empower conference is coming on May 8, 2024, where you can learn more about Exchange as well as other exciting innovations we have coming soon. This is a free, virtual event –sign up today! Action required: Outlook Channel Changes coming December 19th, 2023 One of the most popular Pipelines integrations inQuickbase is the Outlook channel. This channel allows you to move email messages and their attachments, as well as calendar events, into other systems such as Quickbase. It also supports sending emails and scheduling meetings in Outlook automatically. Within the Outlook channel, one key component is the ability to work with shared mailboxes. These are commonly used to collect messages like support requests or orders, in a way that allows a team to access and respond in a timely manner. Based on customer feedback we will be making changes to our Outlook Pipelines and how they work with Shared Mailboxes to create a better and more consistent experience. What is Changing and Who Is Impacted You may need to make changes if you are currently using a shared inbox in an Outlook Pipeline using the following steps: Send an Email Send an Email with Attachments Reply to an Email You can learn more about how these changes impact your existing Outlook Pipelines, the new ways you can use shared mailboxes in Outlook Pipelines, and how to set up your Pipelines to use a shared inbox correctly in the article below. We're releasing these changes with the product release on December 19, 2023. Table of Contents Creating A More Consistent Experience Shared Mailbox field From Address field New Workflows Unlocked Understanding changes to your current Outlook Pipelines Sent Items folder change Permissions change Keeping the exact same behavior of your pipelines Breakdown of changes Creating A More Consistent Experience We've heard from many of you that you would like to have more flexibility in how you work with shared mailboxes. Previously, working with shared mailboxes was only possible in a few steps with strict permission requirements. We are expanding this capability, allowing you to use shared mailboxes in the following steps: Send an Email, Send an Email with Attachments, Search Email, Look Up an Email, New Email, and Search Attachments. Going forward, the Outlook channel will offer two ways to use the functionality of a shared mailbox, with either the Shared Mailbox field or the From address field. Shared Mailbox field This mode allows the user to fully impersonate a shared mailbox account. While using this option, all actions are performed using the shared mailbox account - send, receive, reply, and search. Sent Items will be kept in the Sent Items folder of the shared mailbox . To do so, you must have “Full Access,” in addition to “Send as or Send on Behalf” permissions in the shared mailbox. To use this option in Quickbase, look for the Shared Mailbox field. This field will be available in the following steps: Send an Email, Send an Email with Attachments, Search Email, Look Up an Email, New Email, and Search Attachments. Send, Receive, Reply, Search emails fully impersonating the shared mailbox. Full access in addition to Send as/Send on Behalf permissions are required. Sent items are stored in the shared mailbox’s Sent Items folder within Outlook. From Address field The second option to send emails on behalf of a shared mailbox is to use the From address field. While using this option, all actions are performed using the pipeline builder’s personal Outlook account. Sent items will be kept in the Sent Items folder of the pipeline builder’s personal Outlook account. Microsoft required permissions in this instance are set only to “Send As/Send on Behalf” in the shared mailbox and not “Full Access.” To use this option, look for the From address field in Quickbase. Send email (with attachment) from the personal connected Outlook account on behalf of a shared mailbox. Send as or Send on Behalf permissions are required. Sent items are stored in the builder’s Sent Items folder of their personal connected account.. New workflows unlocked Some builders have not been able to fully use shared mailboxes in Pipelines because they lack the full access permissions in Outlook. If that applies to you, you can now use the From Address field to send emails with attachments from a shared mailbox if you have “Send As/Send on Behalf” permissions in Outlook. You do not need to reconnect to the Outlook channel to do this. Understanding changes to your current Outlook Pipelines In the sections below we will outline how your existing Outlook Pipelines that use a shared inbox may be impacted and the steps you can take to adjust your existing pipelines to avoid issues. Reminder: You may be impacted if you are using a shared inbox in the following Outlook pipeline steps: Send an Email Send an Email with Attachments Reply to an Email Sent Items folder change If you are currently using the Send an Email with Attachments step you may need to update your Pipeline. Specifically, if you have a shared mailbox in your ‘From’ address field the way Sent Items are stored will be changed if you do not make an update. Going forward, the sent items will be kept: For those sending through the Shared Mailbox field – in the Sent Items Folder of the shared mailbox. For those sending through the From Address field – the personal Sent Items folder of the connected builder account. You should take this time to make sure your pipeline is set up to match your needs to avoid any disruption. Permissions change If your pipelines run successfully today and your emails with attachments are properly sent, users in your organization are probably granted full access rights to the mailbox. With the new shared mailbox options, you may want to revisit this with your IT team to see if you would like to take advantage of the new option that works with more limited access rights. These changes do not impact your access to Pipelines. The important change for your workflows remains the change to the Sent Items folder. Depending on the permissions granted, you should decide which field to use with your shared inbox, and make sure you are aware of which Sent Items Folder your sent items will be kept in. Keeping the exact same behavior of your pipelines If you are not sure whether your pipelines are affected by the change, but you want to keep them working in the exact same way as before, you need to: Find those pipelines that include the Send an Email with Attachment step. Check whether you have a shared mailbox entered in the From Address field. If so, fill in the Shared Mailbox field with the shared mailbox that was filled in the From Address. Breakdown of changes Below is a list of all the possible setups for using shared mailboxes and sending on behalf of a different address. Also, each table explains the difference and the changes in the behavior of each step. There are also suggestions for what to do to preserve the setup as it works for you today. Behavior of the Send an Email, Send an Email with Attachment, and Reply to an Email steps before the Dec 19 change: Step If the From field is empty If the From field is filled with a shared mailbox Send an Email Receiver point of view The receiver of the email will see that the email is sent from the email of the currently connected account The receiver of the email will see that the email is sent from the shared mailbox / from the currently connected user on behalf of the shared mailbox (according to the permissions) Where the email will be saved In the Sent Items folder of the mailbox of the currently connected account In the Sent Items folder of the mailbox of the currently connected account Permissions NO additional permissions needed Send As / Send on Behalf permissions to the shared mailbox needed Send an Email with Attachments Receiver point of view The receiver of the email will see that the email is sent from the email of the currently connected account The receiver of the email will see that the email is sent from the shared mailbox / from the currently connected user on behalf of the shared mailbox (according to the permissions) Where the email will be saved In the Sent Items folder of the mailbox of the currently connected account In the Sent Items folder of the shared mailbox Permissions NO additional permissions needed Full access in addition to either Send As or Send on Behalf permissions to the shared mailbox needed If the target email is in the mailbox of the currently connected account (If Shared Mailbox option field is NOT filled in the target step) If the target email is IN a shared mailbox (If Shared Mailbox option field is filled in the target step) If the From field is empty If the From field is filled with a shared mailbox If the From field is empty If the From field is filled with another shared mailbox Reply to an Email Receiver point of view The receiver of the email will see that the email is sent from the email of the currently connected account The receiver of the email will see that the email is sent from the shared mailbox / from the currently connected user on behalf of the shared mailbox (according to the permissions) The receiver of the email will see that the email is sent from the shared mailbox / from the currently connected user on behalf of the shared mailbox (according to the permissions) The receiver of the email will see that the email is sent from the shared mailbox filled in the From field / from the currently connected user on behalf of the shared mailbox filled in the From field (according to the permissions) Where the email will be saved In the Sent Items folder of the mailbox of the currently connected account In the Sent Items folder of the mailbox of the currently connected account In the Sent Items folder of the shared mailbox In the Sent Items folder of the shared mailbox filled in the option field Permissions NO additional permissions needed Send As or Send on Behalf permissions to the shared mailbox needed Full access in addition to either Send on Behalf or Send As permission to the shared mailbox needed Full access in addition to either Send on Behalf or Send As permissions to the shared mailbox filled in the option field and Send on Behalf or Send As permissions to the shared mailbox filled in the From field Behavior of the Send an Email and Send an Email with Attachment steps after the Dec 19 change: Step Shared Mailbox option field is empty Shared Mailbox option field is filled with a shared mailbox If the From field is empty If the From field is filled with a shared mailbox If the From field is empty If the From field is filled with another shared mailbox Send an Email, Send an Email with Attachments Receiver point of view The receiver of the email will see that the email is sent from the email of the currently connected account The receiver of the email will see that the email is sent from the shared mailbox / from the currently connected user on behalf of the shared mailbox (according to the permissions) The receiver of the email will see that the email is sent from the shared mailbox / from the currently connected user on behalf of the shared mailbox The receiver of the email will see that the email is sent from the shared mailbox filled in the From field / from the currently connected user on behalf of the shared mailbox filled in the From field (according to the permissions) Where the email will be saved In the Sent Items folder of the mailbox of the currently connected account In the Sent Items folder of the mailbox of the currently connected account In the Sent Items folder of the shared mailbox In the Sent Items folder of the shared mailbox filled in the option field Permissions NO additional permissions needed Send As / Send on Behalf permissions to the shared mailbox needed Full access in addition to either Send on Behalf or Send As permission to the shared mailbox needed Full access in addition to either Send on Behalf or Send As permissions to the shared mailbox filled in the option field and Send on Behalf or Send As permissions to the shared mailbox filled in the From field *NOTE: The behavior of the Replyto an Email step will remain the same after the change. We are also adding more guidance in the Outlook steps themselves to clearly describe the new shared mailbox functionality. If you have any concerns or need assistance, please don't hesitate to reach out to our support team.