workflow · how to

Edit configuration forms

Follow the edit configuration forms workflow in Slack.

Goal

Edit supported Settings configuration through list and form modals so cadence, CTA, learning, and platform defaults match how your team schedules, publishes, and optimizes content.

When to use this

Use this workflow when you need to change posting windows, CTA config at the domain level, learning settings, or platform capability overrides. Config forms live in the Settings work center. Domains such as UTM defaults, shortlinks, and Link in Bio also have dedicated Settings entries; use those workflows when you only need link and tracking settings.

Before you begin

Confirm these prerequisites:

  • You can open the Settings work center.
  • You have admin or brand management access for the domain you plan to edit.
  • The active brand matches the brand whose overrides you intend to change.

On Team and Scale plans, successful config changes also appear in audit history.

Steps

Open the config picker

  1. Type /social and choose Settings.
  2. Open a settings card that exposes configuration. The config form suite includes Cadence, CTA, Learning, and Platforms.
  3. You can also reach config surfaces through the config picker when it appears in your Settings flow. The picker and Settings hub actions open the expected entry point for each config family.
  4. Pick the config domain and scope when offered: organization, brand, campaign, pillar, platform, or account.
  5. If you see a deprecated config modal, use the current Settings card for that domain instead.

If the modal fails to open because the Slack trigger expired, run the action again from Settings. Trigger expiry is handled safely; no partial save occurs.

Review the list view

Each domain opens a list view first:

  1. Read the effective summary for your selected scope. This shows what the system will apply after inheritance.
  2. Open the form for the scope you want to override.
  3. Confirm you are editing the intended scope before changing fields. Brand overrides do not apply to other brands.

Submit config forms

Cadence, CTA, learning, and platforms each have a dedicated list view and form modal:

  1. Edit the fields the form offers. Cadence forms include posting windows and related scheduling fields when shown. CTA config forms set domain-level CTA behavior separate from the CTA snippet library. Learning and platforms forms cover fields defined for those domains at the scope you selected.
  2. Submit the form. Required fields and structured values are validated before save. Each domain routes through its own submit branch, so errors are specific to the form you opened.
  3. Fix any validation errors shown on the modal. Do not retry with the same invalid value.
  4. Cancel returns you to the list view without saving partial edits.

On success, App Home may refresh or the modal may close depending on context. The change is persisted at the scope you selected.

Understand precedence before stacking overrides

Global defaults apply first. Organization, brand, campaign, pillar, platform, and account overrides replace only the fields you set. Arrays replace entirely; objects merge by field.

Read Configuration inheritance before adding overrides at multiple scopes. A narrower scope wins only for the fields you explicitly set.

Confirm it worked

Run the workflow that depends on the setting and confirm behavior matches saved values:

  • For cadence: schedule or preview a post and confirm it respects your posting windows.
  • For CTA config: open Create and confirm CTA resolution matches the scope you edited.
  • For learning or platforms: trigger the feature that reads those domains and confirm the new values apply.

Terminal save states include saved, active, or skipped depending on the action.

Troubleshooting

Modal did not open

Slack interaction triggers expire after a few seconds. Return to Settings and open the config card again.

Submit shows validation errors

Correct the fields flagged on the form. YAML or JSON values must match the schema for that domain.

Change does not appear within a few minutes

See Configuration change is not applied. A more specific scope override may still be in effect; check inheritance.

You need the full domain list

See the Config domains reference.

You need inheritance rules

See Configuration inheritance.