Know what works in Slack and what opens the web app

Understand native Slack controls, web handoffs, automation templates and the checks that prove real delivery.

Product guide 4 sections

Use native Slack task controls

Commands and interactive controls support basic task creation, task lists, status changes, completion, comments, claiming, update requests, dependencies and calendar summaries/tables. Available actions still depend on current membership and the linked workspace.
Task links open the corresponding web object after sign-in and current access checks. A link is not an invitation or an access grant.
Slack search currently matches task titles and descriptions. The web sidebar and team search support additional metadata; do not expect Slack search to filter every custom field or tag.
Slack task descriptions and comments use Slack's presentation rather than the complete web rich-text editor. Formatting, color swatches and worksheets do not have identical Slack layouts.

Team tag catalogs, tag colors, conditional custom-field definitions, palette configuration, per-color purpose notes, description-snippet configuration and historical snippet sync are managed on the web.
If a team needs required custom fields, Slack task creation hands off to the web form before creating the task. Complete the fields there; opening the handoff alone does not create a task or grant access.
Project Dashboard management, guest codes, guest Viewer/Editor roles, project workflows, card/list/workflow display, column controls and dashboard filtering are web features—not a complete set of Slack modal controls.
Printing job worksheets/PDFs, account security/profile management, promotions and billing administration remain web workflows.
Web descriptions, comments, snippets and task/project views automatically link visible web URLs, preserving formatting. Existing content needs no resave. Links open in a new tab; unsupported or unsafe schemes remain text. This does not change Slack's own text rendering.

/slackalendar subcommands perform supported Slack actions. Automation {{shortcodes}} insert data into status-triggered notification templates. Neither means that every web feature has a native Slack action.
In Settings, choose personal Slack DM categories independently of email, browser sounds and desktop push. Team channel categories are managed separately by the team; they do not use each member's personal opt-in.
Rules can send Slack DMs or linked-channel messages using task, tag, field, color and project shortcodes. Triggering a rule is not proof that Slack accepted or displayed its message.

01Check the selected company, current team membership, workspace installation, personal Slack identity and the team's linked channel. These are separate relationships.
02Review the relevant personal DM or team channel preference, then Recent runs for a rule. Queued or processing is not sent; inspect failures and intentionally skipped results.
03If a feature is web-managed, follow its web link instead of looking for an undocumented slash command. Check required fields before retrying task creation to avoid duplicates.
04Browser and isolated automated tests validate code paths, not every real Slack installation, OAuth permission or delivery receipt. Confirm actual live behavior in an authorized workspace; do not assume it from a saved setting or passing preview.