Key takeaways
- A client should get a scoped role — review and approve, not full publish access.
- A guest approval link avoids the need for a full client seat at all.
- Client-level access should never expose another client’s accounts.
What a client seat should and should not allow
A client reviewing their own content typically needs to see drafts and approve or request changes — not publish directly, change account settings, or manage billing. A real permissions system separates these, rather than an all-or-nothing login.
The guest-link alternative
For most clients, a guest approval link is enough: they review and approve a post without needing a seat, a password, or an account of any kind.
Never let client access cross accounts
Whatever access a client gets should be scoped strictly to their own accounts — a genuine tenant-isolation requirement, not just hiding other clients from a menu.
client accessrolesagency operations
FAQ
- Should a client get full login access to their social accounts in my tool?
- Usually not necessary. A scoped review-and-approve role, or a guest approval link, covers most client needs without full account access.
- What is a guest approval link?
- A link a client uses to review and approve or reject a post without creating an account or being given a login at all.
- Can a client accidentally see another client’s accounts?
- They should not be able to, if client workspaces are genuinely tenant-isolated rather than just visually separated in a list.