When you manage many social media assets, changing the same setting on each one is slow and easy to get wrong. Group settings let you change moderation and permissions settings once, from All assets or from a collection, and save the change to every asset in that view.

Spikerz shows the value most of your assets use, saves your change to the assets that follow it, and lists the assets that are set differently so you can decide, one by one, whether they should match the group or stay as they are.

This guide explains where group settings are available, how the group value is chosen, how to change a setting for a group, and how to review exceptions.

⚠️ Group settings are available on the Business plan and above.

Open the accounts dropdown at the top left of your dashboard and select All assets or one of your collections. The settings of the pages below now apply to every asset in that view.

Each page only includes the assets that support it. For example, Chat moderation covers your YouTube channels only. If none of the assets in the view support a page, it shows None of the assets in this view support these settings.

Every trigger in a group view shows one value: the value most of the assets in the view use. For example, if 8 of your 10 assets scan for Spam and hide matching comments, the Spam trigger shows Active scan and Auto-hide.

Followers and exceptions
Assets that use the group value follow the group. Assets that are set differently are exceptions, and the trigger shows Review exceptions (N) next to its dropdowns, where N is the number of assets that differ.

What is not counted
Assets you chose to keep different, and assets that don't have an AI topic or custom keyword trigger at all, don't count toward the group value.

In the accounts dropdown, select All assets or a collection.

Go to Comments cleaner, Chat moderation, DM protection, or Asset permissions, and open the Settings tab.

Use the trigger's dropdowns, exactly as you would for a single asset:

To change more than the action, open the trigger's ⋯ menu and select Edit trigger. To add a new AI topic, custom keyword, or link trigger to every asset in the view, select Add trigger in that section.

Your change is saved right away to the assets that follow the group. Assets you chose to keep different are left as they are. Deleting an AI topic or custom keyword trigger in a group view removes it from every asset in the view that has it.

If some assets still use a different value after your change, Review exceptions opens so you can decide what happens to each of them. You can also open it at any time from the trigger's Review exceptions (N) link. See the next section.

⚠️ If saving fails for some assets, for example because you no longer have access to them, Spikerz names those assets and leaves their settings unchanged.

The Review exceptions window lists every asset that uses a different value for the trigger. The explanation at the top depends on where you are:

Each row shows the asset, the collections it belongs to, and its Current value. Use the dropdown on the right to choose:

Select Save to apply your choices.

An asset you keep stays as it is the next time anyone changes that trigger for the group, and it no longer counts toward the group value. Spikerz remembers this choice for everyone in your workspace. Kept assets are still listed under Review exceptions, so you can switch them to the group value later.

For AI topic and custom keyword triggers, assets that don't have the trigger show Current: Not added. Choose Switch to … to add the trigger to them, or keep them without it.

Not every platform supports every action. For example, comments on YouTube and TikTok can be hidden but not deleted. In a group view, the Automation dropdown only offers actions that at least one asset in the view supports, and an action is only applied to the assets that support it.

Using a fallback action
When you choose Auto-delete in the Edit trigger or Add trigger window, and some assets in the view can hide but not delete, a switch appears under the action: Use hide as a fallback where delete isn't supported. Turn it on to hide matching comments on those assets instead. Choosing Auto-hide works the same way, with Use delete as a fallback where hide isn't supported.

When some assets delete and others hide as a fallback, the trigger shows Auto-hide/Delete.

Some settings describe one specific account, so they are not part of the group view. Select a single asset to change them.

You can still change settings for one asset at a time. Select the asset in the accounts dropdown, open the Settings tab, and make your change. If that asset now differs from the rest of a group, it is kept as an exception in that group's view, so a later group change doesn't overwrite it.

The Apply to all assets checkbox is still available in a single asset's trigger, brand voice, knowledge, and asset context windows when you want to copy one asset's setting to all your assets.

A group change only reaches the assets you have access to. To learn more about roles, see Spikerz Workspace Roles.