workflow · how to

Manage roles, routing, and audit history

Follow the manage roles, routing, and audit history workflow in Slack.

Goal

Assign roles, configure where review work routes in Slack, and review or export audit history for your organization. These controls live in the Settings work center and affect what teammates see in App Home, who can approve content, and what actions are recorded.

When to use this

Use this workflow when you onboard a new teammate, change who can approve or create content, adjust review handoff channels, or need a record of settings changes for compliance. Open the audit log when you need to verify who changed what and when, or when you need to export history for review outside Slack.

Before you begin

You need admin access or roles management permission for role and routing edits. Governance entry paths check roles management permission before opening edit surfaces.

For audit export, you need audit export permission. Audit history viewing and export are available on Team and Scale plans. SIEM export also depends on SIEM configuration in your organization.

Know which scope you are editing: organization-wide roles differ from roles scoped to a brand, pillar, or campaign. Have the Slack channel IDs or names ready when you configure review routing.

Steps

Open governance areas

  1. Type /social and choose Settings.
  2. Under Billing/Admin, open Roles & Permissions to manage role assignments.
  3. Open Team from Settings when you need the combined team modal that includes member and role management.
  4. Choose View audit log from the same area when you need history rather than live edits.

The Settings hub is the primary entry point. Team management and audit log each open their own modal surfaces.

Edit roles

  1. Open the roles editor for the organization or scoped entity shown in the modal.
  2. Adjust assignments for the roles offered at that scope: admin, owner, manager, approver, creator, or viewer.
  3. Submit the form.

Invalid role or scope values return field errors in the modal. Partial changes are not applied when validation fails. Successful role updates write audit records and refresh the permission state used across App Home, so teammates may need to reopen App Home to see updated capabilities.

Decide scope before you submit. An approver at the brand level cannot approve content for a different brand unless they also hold a role there.

Edit review routing

  1. Open routing settings from the governance or workflow settings entry when it appears in your Settings hub.
  2. Set channels and scope combinations for review handoffs. Each route ties a scope (such as a brand or campaign) to a Slack channel where review notifications land.
  3. Submit after reviewing channel and organization consistency.

Conflicting routes are rejected in the modal with field-level errors. Fix the flagged combination and submit again. Saved routing takes effect for new review items; items already in flight keep their existing route.

Review and export audit history

  1. Open the audit log viewer from View audit log in Settings.
  2. Browse entries with Previous and Next. Filters stay attached to your session as you page.
  3. Export when your permissions and plan allow:
    • CSV for spreadsheet review
    • JSON for structured processing
    • SIEM when SIEM delivery is configured for your organization

Large exports may arrive as a follow-up Slack message or file link rather than inline in the modal. Wait for the delivery message before assuming the export failed.

Confirm it worked

Ask a teammate to open App Home and confirm their available actions match the role you assigned. A creator should see create actions; an approver should see approval surfaces; a viewer should not see edit or approve controls they did not have before.

Trigger a settings change you made (such as a role update) and open the audit log. Confirm a row appears with your user, the action name, and a timestamp that matches when you saved.

For routing changes, send a test item into review and confirm the notification arrives in the channel you configured.

Troubleshooting

You cannot open Roles & Permissions or the roles editor. Confirm you hold admin access or roles management permission. Ask an existing admin to grant the role or perform the change.

Submit returns field errors on roles. Check that each assignment uses a valid role for the scope shown. Remove duplicate or conflicting assignments and submit again.

Routing submit rejects your channel. Verify the channel exists in the same Slack workspace where Slash Social is installed and that the bot can post there. Conflicting scope and channel pairs must be resolved before submit succeeds.

Audit log is empty or missing recent events. Refresh the viewer and page forward. Very recent changes may take a moment to appear. Confirm you are viewing the correct organization scope.

Export buttons are missing or export fails. Audit history export requires Team or Scale plan access and audit export permission. SIEM export requires SIEM configuration. Contact your billing owner if you need plan access.

Teammate still sees old permissions after a role change. Ask them to close and reopen App Home. Permission state refreshes on the next App Home load.