Skip to content
Platform

One organisation. A workspace for every brand.

Trabbly Social keeps each brand's accounts, calendar, approvals and results in its own workspace, under one organisation with roles you control.
Take the tour
Your organisation
Synced
How it's organised

Organised the way agencies work.

Your organisation is the top level: your agency or company. Inside it, every client or brand gets its own workspace, and each social account connects to exactly one brand.

Organisation

Your agency or company

  • People and roles
  • Agency branding
  • Every brand workspace
  • FitnessBrand workspace
    Accounts
    LinkedInXYouTube
    Approval
    Internal + client
    Calendar and results
    Its own
  • CaféBrand workspace
    Accounts
    InstagramFacebookLinkedIn
    Approval
    Internal only
    Calendar and results
    Its own
  • HotelBrand workspace
    Accounts
    XTikTokYouTubeInstagram
    Approval
    Internal + client
    Calendar and results
    Its own
  • FintechBrand workspace
    Accounts
    LinkedInGoogleFacebook
    Approval
    Internal + client
    Calendar and results
    Its own

Illustration: example brands and accounts.

Each account belongs to one brand

A social account connects to a single brand, and the same account can't be connected to two brands in one organisation. That keeps every brand's calendar, approvals and results cleanly its own.

  • Organisation

    Your agency or company: its people, roles and branding.

  • Brand workspace

    One per client or brand, with its own accounts, calendar, approval rule and results.

  • Connected account

    A Page, profile or channel, signed in through the network's own page.

People and roles

The right access for every role.

People get a role in the organisation and a role on each brand they work on. Clients review in their own portal and never see your workspace.

Organisation roles

  • Owner and admin

    Everything on every brand, including internal approval, scheduling and managing accounts.

  • Member

    Works on the brands they're added to, with a brand role on each.

  • Client

    Reviews what's sent to them in the client portal. Clients don't count as team members.

Brand roles

Brand roles and what each can do
Brand roleCreateEditSubmitApprove internallyPublish and scheduleAnalyticsManage accounts
Brand managerSame as owner and adminYesYesYesYesYesYesYes
StrategistYesYesYesNoNoYesNo
WriterYesYesYesNoNoNoNo
DesignerNoYesNoNoNoNoNo
PublisherAlso recovers failed publishingNoYesNoYesYesYesNo
AnalystNoNoNoNoNoYesNo
ClientReviews content sent to them in the client portal, and nothing else.

Swipe the table sideways to see every column.

  • Every permission is checked on the server, not just hidden in the interface.
  • Clients never see the agency workspace or other clients.Trabbly for agencies
Product tour

Five modules, one workflow.

Each module hands work to the next: accounts feed the composer, the composer feeds review, and only approved versions reach publishing.

Module 01

Connect accounts

Sign in on each network's own page, then choose which of the Pages and accounts it finds to connect to a brand. Trabbly never asks for, or stores, a social password.

  • Official sign-in (OAuth) for every network
  • You pick which discovered accounts to connect
  • Each account shows a status and a plain reason, re-checked hourly
Synced
Post lifecycle

Always know where a post stands.

Every network version of a post carries its own status, so the whole team sees what is waiting, what is going out and what needs a person.
  1. Draft

    Saved and editable. Nothing is sent anywhere.

  2. In review

    Internal review, then the client if the brand requires it.

    • Changes requested

      A note says what to change. The edit becomes a new version and returns to review.

  3. Approved

    Signed off on this exact version, and only this one.

  4. Scheduled

    Queued for a local time in a chosen time zone.

  5. Publishing

    Being sent to the network now.

    • Failed

      The network refused it. The reason is shown.

    • Outcome unknown

      No answer. The account is checked before any retry.

  6. Published

    The network accepted the post.

Approval never guarantees publication: a network can still refuse an approved post, and it then shows as failed with the reason.

Security and data

Kept separate by design.

Each organisation's data is walled off from every other, every action is checked on the server, and social passwords never touch Trabbly.
  • Isolated per organisation

    Each organisation's data is kept apart in the database itself (row-level security).

  • Checked on the server

    Every request is checked against the person's role before anything happens.

  • No social passwords

    Accounts connect through each network's official sign-in. Trabbly never asks for or stores a password.

  • A record of what happened

    Connections are re-checked hourly with a history, and every publish attempt is kept with the network's response.

Say hello to Trabbly.

Book a relaxed walkthrough shaped around your brands, networks and the way your team signs things off. We'll show you what's live today, what's coming next, and how it would fit the work you already do.
  • Shaped around your brands
  • Honest about what's live
  • No social passwords, ever
Compare plans