Docs: Social Premium trigger defaults (SM-3876)

[cursor]

JIRA

• SM-3876 - Trigger Settings Default Value

Reviewers / stakeholders

@ahnikakuse @haleyserrano @maryam6samadi

Change classification

• Feature behavior change
• Configuration / system behavior

Summary of documentation updates

Updated the existing AI Workforce overview to document the default trigger settings applied when Social Premium is activated for the Social Media Manager and Blogger AI Employees:

• Weekly frequency
• Activation-day day of week
• 9:00 AM time
• Business timezone with Chicago fallback
• Activation-date start date
• No end date

Existing docs updated or new docs created

• Updated existing page: docusaurus/docs/ai/ai-workforce/index.mdx
• No new page was created.

Placement reasoning

Discovery found an existing AI Workforce overview and no dedicated Social Marketing, Blogger, or trigger settings page. The change describes default configuration for AI Employees, so the AI Workforce overview is the closest existing location and avoids creating an isolated page for a narrow behavior update.

Acceptance criteria coverage

Acceptance criterion	Documentation coverage
Frequency defaults to Weekly	Documented in the default trigger settings list
Day of week defaults to product activation day	Documented in the default trigger settings list
Time defaults to 9:00 AM	Documented in the default trigger settings list
Timezone defaults to business timezone	Documented in the default trigger settings list
Falls back to Chicago timezone if business timezone is unavailable	Documented in the default trigger settings list
Start date defaults to product activation date	Documented in the default trigger settings list
End date defaults to No / no end date	Documented in the default trigger settings list
Applies to Social Media Manager and Blogger AI Employees	Documented in the opening sentence of the new section
Consistent across web and mobile	Not separately documented because the docs describe the shared default behavior, not platform-specific UI steps

Figma / images used

• Jira included screenshot attachments, but the attachment URLs require authenticated Jira access and were not accessible in this environment.
• No Figma links were present in the webhook payload.
• Documentation was based on the Jira story description, acceptance criteria, and comments.

Skills and tools used

• Repository discovery with Glob and rg
• Existing documentation inspection with ReadFile
• Jira automation memory review via AutomationMemory
• No specialized repository skill applied; the available skills target getting-started guides, overview page expansion, screenshot redaction, side-by-side images, and sprint-review transcript updates, none of which fit this narrow existing-page update.

Related implementation PRs / code authors

• The Jira development field indicated one merged GitHub PR, but did not include a PR URL or author in the webhook payload.
• gh search prs did not find PRs for SM-3876, SM-3723, Trigger Settings Default Value, AI Blogger, or related Social Premium trigger phrases.
• Atlassian MCP requires authentication in this environment, so no additional Jira-linked PR details could be retrieved.
• No related code-change authors were tagged because no Vendasta GitHub handles could be verified.

Assumptions and limitations

• Assumes the Jira Done status reflects the behavior intended for documentation.
• A later Jira comment reported production values were not properly updated for a specific PID/AGID; this PR documents the accepted default behavior from the story and should be reviewed against the final shipped implementation.

Validation

• npm install completed successfully.
• npm run typecheck was attempted and failed on existing TypeScript issues outside this documentation change:
  • src/theme/Root.tsx: HTMLElement property errors for type and text
  • src/theme/TOC/index.tsx: missing module/type declaration for @site/src/components/PageActions