D
Daniel Fundi Ndaya
The Problem
GoKollab communities should not depend entirely on individual user accounts.
What happens when the person who created a community leaves the company, resigns, passes away, becomes incapacitated, or loses access to their account?
Organizations could lose access to communities containing thousands or millions of members, content, subscriptions, and other valuable assets.
Platforms like Facebook and LinkedIn already distinguish between personal profiles and company pages. A person can manage multiple organizations, while those organizations maintain their own identity and assets.
GoKollab needs a similar structure to become scalable for enterprises, schools, franchises, nonprofits, and other organizations.
Proposed Solution
Introduce two separate account types:
1. Personal Accounts
Every user has an individual GoKollab profile.
Users should be able to:
  • Create and manage their personal profile.
  • Join communities.
  • Create personal communities.
  • Create company/organization accounts.
  • Join multiple organizations.
  • Manage organizations they have permission to access.
  • Switch between personal and organizational accounts.
  • Maintain their personal identity independently of any organization.
One personal profile should be able to work with multiple companies without requiring separate logins.
2. Company/Organization Accounts
Allow users to create dedicated accounts for companies, universities, schools, churches, nonprofits, government institutions, and other organizations.
Each organization should have:
  • Its own public profile, logo, branding, and information.
  • Multiple administrators and employees.
  • Teams, sub-teams, and organizational roles.
  • Granular permissions.
  • Multiple organization-owned communities.
  • Centralized community management.
  • Organization-level billing and subscriptions.
  • Centralized analytics and reporting.
  • Ownership verification and recovery procedures.
  • Independent ownership of its communities and digital assets.
The organization should own its communities, not the individual employee who created them.
  1. One Organization, Multiple Communities
An organization should be able to create and manage multiple communities under one account.
For example, a university could have:
  • Main University Community
  • Student Community
  • Alumni Community
  • Faculty Community
  • Engineering Department
  • Business School
  • Sports Community
Each community can have different administrators, moderators, members, and settings.
However, all communities remain under the university's ownership.
Organization administrators should be able to oversee all communities without needing access to employees' personal accounts.
4. Users Can Manage Multiple Organizations
A single user should be able to belong to multiple organizations with different roles.
For example, John could be:
  • An administrator at Company A.
  • A community manager at Company B.
  • A moderator at Company C.
  • A member of Company D.
  • The owner of his own personal community.
John should use one personal account and switch between organizations as needed.
Introduce an organization switcher similar to Facebook Pages, LinkedIn Company Pages, or Slack workspaces.
When switching organizations, the user should see only the resources and administrative functions they are authorized to access.
5. Organization Roles & Permissions
Support organization-level roles such as:
  • Organization Owner
  • Organization Administrator
  • Community Administrator
  • Community Manager
  • Moderator
  • Content Creator
  • Member
  • Custom role
Allow custom roles and granular permissions.
For example, an organization administrator can manage all communities, while a community manager can manage only specifically assigned communities.
Users should also be able to create communities on behalf of organizations when granted permission.
6. Ownership, Succession & Business Continuity
This is critical.
Organizations should never lose their communities simply because an employee becomes unavailable.
Support:
  • Multiple authorized organization administrators.
  • Secure ownership transfers.
  • Administrator succession.
  • Removing employees without losing community access.
  • Reassigning communities to new managers.
  • Organization ownership verification.
  • Secure recovery when all administrators become unavailable.
  • Audit logs for ownership and permission changes.
The organization must retain control over its communities, members, content, and business assets regardless of employee turnover.
7. Personal vs. Organization Communities
When creating a community, users should choose whether it belongs to:
Personal Account:
Individually owned and managed.
Organization Account:
Owned by the organization and managed by authorized users.
Allow authorized transfers of personal communities to organizations.
Organization-owned communities should remain with the organization when their creators leave.
8. Public Organization Profiles
Organizations should have public-facing pages similar to LinkedIn Company Pages.
These pages could display:
  • Organization branding and information.
  • Public communities.
  • Courses.
  • Events.
  • Membership offerings.
  • Announcements.
  • Departments or associated brands.
Users should be able to discover organizations, follow their profiles, and join their communities.
9. Centralized Organization Management
Organizations should be able to manage multiple communities from one dashboard, including:
  • Community creation and administration.
  • Team and user management.
  • Roles and permissions.
  • Organization branding.
  • Billing and subscriptions.
  • Content and digital assets.
  • Consolidated analytics.
  • Community ownership and access.
10. API Support
Provide APIs for managing organizations, members, roles, permissions, organization-owned communities, administrator assignments, and organizational resources.
This would enable integrations with CRMs, HR platforms, school management systems, and enterprise identity providers.
Why This Matters
A multinational corporation, university, franchise network, or church organization may operate hundreds or thousands of communities.
These communities cannot sustainably depend on individual employee accounts.
Organizations need centralized ownership with decentralized administration.
This would allow GoKollab to scale beyond individual creators into a platform supporting entire organizations and their digital communities.
The Opportunity for HighLevel
This would establish the foundation for enterprise community management, multi-brand organizations, franchise networks, universities, and other large institutions.
Facebook separates Profiles from Pages. LinkedIn separates Personal Profiles from Company Pages.
GoKollab should similarly separate personal identities from organizational ownership while allowing users to work across multiple organizations.
The ultimate goal: People manage communities, but organizations own them. Employees may come and go, but the organization's communities, members, content, and digital assets should remain secure and operational.