Skip to main content

Social Ideate and Studio

Ideate turns plans into briefs; Design Studio produces approved creative stored in Assets. Together they prevent off-brand posts and give approvers a clear queue before Composer scheduling.

Video

Video coming soon for this topic

Who can do this​

Content strategists, designers, approvers.

Before you begin​

  • Social setup done
  • Active Plan in /social/plan/planning
  • Roles: who writes brief vs who approves creative

What you'll accomplish​

  • Brief approved in Brief Approvals
  • Finished asset in Assets library
  • Handoff package ready for Composer

Step-by-step procedure​

Ideate workflow​

  1. Worksheet (/social/ideate/worksheet)—fill rows: theme, copy angle, networks, due date.
  2. Submit for Brief Approvals (/social/ideate/approvals).
  3. Approver selects Approve or request changes with comments.
  4. Approved rows unlock Studio work.

Design Studio workflow​

  1. In Studio (/social/studio/in-studio)—open assigned brief.
  2. Produce images/video/carousel per network specs.
  3. Send to Creative Approvals (/social/studio/approvals).
  4. On approval, publish asset to Assets (/social/studio/assets).
  5. Tag asset with campaign/plan for search in Composer.

Collaboration tips​

  • Keep worksheet statuses honest (Draft / In review / Approved).
  • Store source files in Files if larger than Social asset limits.
  • Reference Knowledge Hub snippets for regulated industries.

Extended guidance​

Worksheet rows should link to Plans IDs so Impact reports roll up by campaign theme. Designers: export finals to Assets with consistent naming (2026Q2_product_launch_ig_carousel). Rejections in Creative Approvals need written reasons—reduces resubmit loops.

Practice scenarios​

Reject a brief once with written feedback, resubmit, approve, complete In Studio, land asset in Assets.

Sandbox validation​

Repeat the procedure in a test workspace or with two internal colleagues before customer-facing launches. Document who approved each step (marketing, legal, ops). Screenshot Verify your work outcomes for audit trails. When something fails, capture the URL, role, timestamp, and exact UI label clicked—Support resolves tickets faster with that context. Re-read See also links after your first successful run; adjacent topics often cover edge cases you have not hit yet.

Team rollout checklist​

Assign a single owner for this workflow per workspace. Schedule a 30-minute handoff training with screen share. Add the See also links to your internal Notion or wiki. Re-verify after each major product release (labels move occasionally). Pair junior staff with a senior reviewer for the first live execution. Log lessons learned in your team retro—especially permission surprises and integration timeouts.

Keep learning​

Bookmark this page and the Product module map. After major releases, re-walk Step-by-step procedure—UI labels move occasionally. Share feedback with your workspace Admin so Help stays aligned with how your team actually works.

Verify your work​

  • Brief moves from pending to approved
  • Asset thumbnail visible in Assets
  • Composer can attach asset without re-upload

Tips​

tip

Agencies: mirror client approval SLAs in worksheet due dates so Publish Queue does not stall.

Troubleshooting​

| Brief stuck | Assign approver in Setup workflow | | Asset rejected | Check network dimension requirements in brief | | Duplicate assets | Dedupe in Assets before scheduling |

See also​