Different apps expose different work
Work Mode uses the capabilities available to the signed-in user, not a generic “edit anything” command. A question about an app may be answerable from authorized records even when there is no dedicated Work action to change that app’s settings.
Use this directory to separate three outcomes: a sourced read, a prepared change with approval, and a plan you complete in the owning app. App ownership, team access and connection health still apply to each task.
Native workflows with specific controls
- Site Spark forms — create or duplicate drafts, edit supported copy/style/field order, and separately review publishing or archiving.
- Site Spark settings — inspect saved booking, chat, theme, CRM or embed configuration; change unsupported settings in Site Spark.
- Close Forge setup — prepare a disabled deployment and two-touch workflow from a selected supported CRM account.
- Close Forge improvements — analyze configuration and prepare selected version-bound draft edits.
- Close Forge lifecycle — review configuration, publication, pause, resume and archive consequences.
- Lead Forge reporting and tracking campaigns — distinguish local records from live advertising.
- Contacts and lead notes — find an exact record, change a local display name or append a scoped internal note.
- One-to-one messaging — prepare one editable SMS or email and verify its send state.
- Property Intelligence — query numeric property fields and preserve modeled-value and coverage qualifications.
Context and owning-app handoffs
The guides for CallSpark and Vulcan Voice, Proof Pulse, Map Forge and Vulcan Score explain how to use available context and prepare useful work without inventing dedicated settings or publishing controls.
For Web Spark, use the website’s own Studio for its specialist planning, review and release flow. Customer websites managed through GitHub, Vercel or Desktop Commander use different, explicitly connected Work paths.
A quick test before you ask for changes
For this app and selected deployment, show the actions currently available to me. Separate read-only tools from changes that require approval. Do not execute or prepare a change yet.
This asks for the current authorized catalog. If the required action is absent, continue in the owning app or ask support about availability. A plugin appearing in the gallery, a product appearing in navigation, or an old successful conversation does not establish today’s permission to execute.