Currently, a Zernio user account can only belong to one team/organization at a time. Accepting an invitation to a new team overrides access to the previous team, removing the user from the original workspace entirely.
For agencies, freelancers, and external consultants managing multiple clients, this restriction creates significant friction:
Client Ownership Limitations: Clients want to own their Zernio account, billing, and subscription for security and autonomy reasons, rather than relying on an agency-owned profile/workspace.
Account Overrides: Being invited to a client’s team revokes access and email notifications (e.g., webhook failure alerts) for all previous client teams.
Inconvenient Workarounds: Managing multiple email addresses or logging in and out of individual client accounts continuously is inefficient and error-prone.
Implement Multi-Team Membership and an Organization/Team Switcher (similar to platforms like Make.com, GitHub, or Slack):
Multi-Team Invites: Allow a single Zernio user account (identified by one email address) to accept invites from multiple independent organizations/teams simultaneously without overriding existing access.
Workspace / Team Switcher: Add an in-app dropdown in the UI navigation that enables users to seamlessly toggle between all teams they belong to.
Granular Permissions & Scope: Ensure user permissions and notification settings (such as webhook failure alerts) remain scoped to each respective organization.
Target Users: Freelancers, agencies, and cross-functional consultants managing integrations or social accounts on behalf of multiple clients.
Business Value:
Improved Client Onboarding: Clients maintain ownership and billing control of their accounts while granting access to external agency partners.
Enhanced Security: Avoids credential sharing or requiring agencies to host client assets under a single master agency account.
User Retention & Satisfaction: Aligns Zernio with standard modern SaaS multi-tenant design, removing a major blocker for agency adoption.
Profile-per-Client Model: Client social accounts live inside the agency’s single team. Drawback: Clients lose ownership/control of their Zernio account and depend entirely on the agency.
Multiple Logins: Creating separate Zernio accounts per client. Drawback: Friction from constantly switching credentials and managing multiple email accounts.
Please authenticate to join the conversation.
In Review
Feature Request
About 1 month ago

asafm7
Get notified by email when there are changes.
In Review
Feature Request
About 1 month ago

asafm7
Get notified by email when there are changes.