getting started · tutorial

Invite teammates and assign roles

Set up invite teammates and assign roles during your first Slash Social workspace run.

Goal

Invite teammates to your Slash Social organization and assign roles so creators, approvers, and brand owners see the right work in Slack. When you finish, each person can open App Home, see the correct brand, and complete the tasks you assigned.

Before you begin

You need a working brand. Finish at least one draft through review before you invite a large team so workflows and routing are stable.

You need permission to manage roles. Organization admins and users with roles management access can open the team and roles surfaces from Settings.

Decide who needs each type of access before you invite:

  • Creators draft and edit content
  • Approvers and reviewers approve or reject posts
  • Managers and owners manage brand settings, billing, or governance
  • Viewers need read-only visibility

Roles are scoped to the organization and brand. A user can hold different roles on different brands when your org uses multiple brands.

Team and Scale plans include audit history and review reason governance in Settings for admins who need compliance controls. Assign those surfaces only to people who should export audit logs or edit review reasons.

Steps

  1. Type /social and choose Settings.
  2. Confirm the active brand matches the team you are configuring.
  3. From the Settings hub, open Roles, Team, or Manage roles (labels depend on your Settings layout).
  4. Add the teammate by Slack user or email, following the prompts in the team modal.
  5. Assign a role that matches their job:
    • Owner for brand owners who manage settings and billing
    • Manager for leads who approve and configure workflows
    • Publisher for users who schedule and publish approved content
    • Reviewer or Approver for approval-only access
    • Creator for drafting content
    • Viewer for read-only access Brand Members views may show a subset of these labels; pick the closest match to the access they need.
  6. Save the assignment. Governance flows validate scope and role payload before changes apply.
  7. Ask the teammate to open Slash Social App Home and confirm they see the brand and work centers you expect.
  8. Repeat for each brand if the user needs different access per brand.

For ongoing changes to routing rules or audit exports, see Manage roles, routing, and audit history.

Confirm it worked

The teammate opens /social or App Home and sees the assigned brand. They can complete a task that matches their role:

  • A creator can start a draft from Create
  • An approver can open pending approvals
  • A manager can open Settings surfaces you expect them to manage

If they should not see billing or governance controls, confirm those buttons are hidden on their App Home.

Next step: Read Roles, personas, and permissions to map job titles to product access, or continue onboarding with Connect your first social accounts.

If something goes wrong

Roles or Team does not appear in Settings

You may lack roles management permission. Ask an organization admin to grant roles management access or perform the assignment for you.

Save fails or shows a validation error

Confirm you selected a valid scope (org or brand) and a supported role for that scope. Close the modal, reopen Manage roles, and retry with a single role change.

Teammate sees the wrong brand or empty App Home

Ask them to refresh App Home. Confirm they were added under the correct brand. If they belong to multiple brands, have them switch the active brand from App Home.

Teammate cannot approve or create despite a role change

Role changes can take a moment to apply. Have them close and reopen App Home. Confirm you assigned a role with the needed capability (for example, approver versus viewer).

You need audit or review-reason access

Audit history and review reason governance are available on Team and Scale plans. Upgrade if those surfaces are required and missing from Settings.

For deeper governance tasks, follow Manage roles, routing, and audit history.