You’re likely familiar with the Bulk Update (ti ti-truck) icon found on many grids throughout Rock. However, when you’re viewing a Connection Type—found at People > Connections > "Connection Type"—this tool gains some specialized superpowers. Instead of standard data changes, these options are tailor-made for managing connection requests at scale. Let’s explore how these specific tools can streamline your workflow. Campus Filter - If you have multiple campuses, bulk updates to connection requests can only be performed one campus at a time. This is where you select which campus’s requests you want to update.Optional Updates - Here you can choose to change the opportunity, status or state for the connection requests. Just like other bulk update screens, you need to click in the small circle next to Status and State to update these fields. Connector - Select whether to keep the current connector, keep the default connector, select a connector from the configured list of connectors or assign no connector.Launch Workflow - If a workflow type is selected, then one workflow will launch for each connection request. The connection request itself will be passed to the workflow using a key of Request. Add Activity - You can optionally choose to add an activity to the selected connection requests. Clicking the Add Activity checkbox will cause the other activity fields to appear. List View Bulk Updates From the Connections List View, Bulk Updates are built in. If you select any checkbox on the grid, an action bar will pop up. From the action bar, there are many things you can do: ti ti-user-circle Assign - Use this to quickly hand off selected requests to a specific connector. It's the best way to balance the workload across your team or ensure a person is matched with the right leader.ti ti-select Change Status - This allows you to update where several people are in the process at once. If your organization uses Sequential Mode, the system will smartly guide you by only showing the next logical steps available.ti ti-circle-check Complete - When a person has successfully reached the end of their connection journey, use this to mark their request as finished and celebrate the win. ti ti-dots-vertical More - Click this to see additional actions.ti ti-user Set as Active - If a request was previously set to follow-up or even set as Inactive, this button brings it back into the immediate queue so connectors know it's time to re-engage.ti ti-user-off Set as Inactive - Sometimes a connection doesn't move forward right away. Marking it inactive keeps your workspace clean without losing the history of that person's story.ti ti-calendar Set as Future Follow-Up - Think of this as a snooze button. It "freezes" the request and hides it from view until a specific date you choose, ensuring you reach back out exactly when the time is right.ti ti-trash Delete - While we rarely want to remove a person's history, this option is there if a request was created by mistake, or is truly irrelevant. Just remember that this action is permanent. ti ti-message-circle-plus Send SMS - This opens up a quick message sender for everyone you've selected. It’s the fastest way to send a personal text or a quick update to a group of people simultaneously.ti ti-mail-plus Send Email - When you have more to say, use this to draft a bulk email. You can use system templates to keep things consistent or write a fresh message to guide your people toward their next steps.ti ti-activity Add Activity - This is your way of keeping the history book updated. Use it to log a specific interaction—like a phone call or a coffee meeting—for several requests at once. It ensures that anyone who looks at these records later knows exactly where the relationship stands. Trailblazer ti ti-settings-cog Launch Workflow - This is a powerful tool for automation. You can trigger specific processes—like background checks or automated welcome emails—for everyone you've selected simultaneously. You can only run Workflows that have a Trigger Type of Manual. Trailblazer Handling Exceptions Trailblazer When you are taking action on a bunch of requests at once, some are bound to have exceptions. Below we have an example where we've bulk selected individuals from different opportunities. Trailblazer Each opportunity has different Workflows available, meaning when we try to run a Workflow that is limited to one opportunity on requesters who are in multiple, it won't work on every one of them. No need to sweat it since Rock handles it elegantly. Trailblazer Above you can see that when we ran this bulk Launch Workflow action it says "The 'Photo Release' workflow is being started for 2 of the 3 selected connection requests". Rock will make it clear whether the bulk action you ran worked as expected, so you aren't left guessing. NoteBulk Status Updates in Sequential ModeWhen sequential mode is enabled on the connection type, the bulk‑update UI changes to a linear flow. Users must process statuses in order and cannot skip ahead.