concept · explanation

Organizations, workspaces, and brands

Understand how organizations, workspaces, and brands works in Slash Social.

Slash Social separates billing, Slack installation, and content identity. Knowing which layer owns a setting or limit prevents wrong-brand posts, surprise quota blocks, and permission confusion.

Overview

Three layers stack above every Slack action:

  • An organization owns billing, usage limits, plan access, and shared resources.
  • A Slack workspace is one app installation context inside that organization. Multiple workspaces can belong to the same org and share billing.
  • A brand is the content identity: connected social accounts, pillars, campaigns, timezone, approvals, and calendars.

Most user-facing content operations follow the active brand. Most billing and plan decisions belong to the organization. Workspace context matters for which Slack installation and App Home preferences apply, but it does not split billing.

How it works

When you open /social, Slash Social identifies your organization from the Slack workspace you are in. Your active brand drives create, plan, inbox, and insights views. Switching brands in App Home changes which accounts, drafts, and counts you see without changing the organization subscription.

App Home preferences, such as calendar view, inbox tab, and work center preference, are saved per user, workspace, and brand. The same person in two workspaces of one organization can keep different UI preferences in each Slack team.

A brand includes:

  • Accounts: connected social profiles scoped to that brand.
  • Pillars and campaigns: taxonomy and launch groupings for planning.
  • Items: drafts and scheduled posts tied to the brand.
  • Configuration: cadence, voice, and other settings for that brand and its campaigns or pillars.

Roles and permissions attach to the organization, a brand, a pillar, or a campaign. The same person can be a creator on one brand and an approver on another. Governance settings in Settings show who can manage brands, roles, and billing.

Organizations with more than one brand use brand switching so teams do not mix client work. Portfolio views and brand selectors use the same organization boundary: usage still counts once at the organization level even when you switch brands.

Billing surfaces (Billing & Plan, usage, upgrades) always reflect the organization. Connecting a social account counts against org profile limits even when the account belongs to a specific brand.

Examples

An agency organization installs Slash Social in two Slack workspaces for different client teams. Both workspaces share one subscription and one AI generation counter. Each workspace user picks an active brand before creating posts.

A single-brand company has one default brand. Creators rarely switch brands, but approvals, inbox items, and analytics still show work for that brand.

An admin invites a freelancer as creator on Brand A only. That user cannot approve posts for Brand B because role assignments are specific to the brand, not workspace-wide defaults.

A company connects social accounts during onboarding in one workspace, then installs the app in a second workspace for another department. Both installations map to the same organization, so profile limits and billing stay unified while brands keep content separated.

See Set up your first brand for the onboarding path that creates your initial brand inside a new organization.