Per-client approver scoping

Why scope per client

If you run social for multiple clients, each client's reviewer should see only their own brand's drafts — not the others. Per-client scoping makes that automatic.

How it works

When you invite an approver, choose Specific clients only and pick which client profiles they can see. The approver's account is bound to those clients only:

• They see posts in /approvals only when the post has a matching client tag
• They can't read other clients' posts even by URL — RLS blocks it at the database
• The approval gate in the composer hides the toggle when no eligible approver exists for the selected client

All clients vs specific clients

Scope	When to use
All clients	Internal manager / agency owner who reviews everything. Default for backwards compatibility.
Specific clients only	A client's own reviewer. They sign off only on their own posts.

A single email can hold either an "all clients" row OR multiple per-client rows for one owner — not both. If you try to mix, the invite errors. Revoke the old one first if you need to change scope.

What happens to existing all-clients approvers

If you set up approvers before per-client scoping existed, they're all "All clients." That's the same behavior they had before. To scope one of them per-client now:

1. Revoke the all-clients access
2. Re-invite with Specific clients only and pick the right ones

In-place scope editing isn't supported yet.

Multi-client invites

If you pick more than one client when inviting, SocialCal creates one approver row per client and bundles them under a single invite token. The approver clicks one link to accept all scopes at once.

Email fan-out

When you flag a post for client X, only approvers eligible for client X receive the awaiting-approval email:

• All-clients approvers (always)
• Approvers scoped specifically to client X

Approvers scoped to other clients don't receive the email and don't see the post.