A complete public foundation
Present a name, photo, cover, headline, bio, location, social links, interests, skills, languages, and the profile sections you choose to publish. Discovery and contact visibility remain controlled rather than assumed.
Build one public Sapeans identity with experience, learning, skills, creative work, projects, credentials, and investor context.
Repeating a thin profile in every community loses the work, interests, and experience that make a person understandable. Sapeans uses one account-level profile across the platform and community presentations, then layers local membership details, custom fields, and visibility choices around it instead of creating a second professional identity.
Present a name, photo, cover, headline, bio, location, social links, interests, skills, languages, and the profile sections you choose to publish. Discovery and contact visibility remain controlled rather than assumed.
Add professional experience, education, credentials, recognition, volunteer work, publications, and speaking artifacts. Empty repeatable rows are not treated as public profile content.
Create projects through Details, Story, and Finish. Modular text and media blocks support a richer case study, while outcomes, results, credits, disclosure, and discoverability are handled before publishing.
Credits can link to public Sapeans profiles or use a manual fallback. Linked collaborators receive a request and decide whether the canonical project appears in their own portfolio; the owner remains the canonical source.
Creator & Media uses platform-backed channels and audience context. Investor profiles can present thesis, sectors, stages, geographies, cheque range, lead/follow preference, involvement, and confirmed public company relationships without exposing private deal economics.
Set the public basics and choose what should be discoverable.
Build the professional, learning, creative, volunteer, and interest sections that fit you.
Publish projects, artifacts, credentials, or an investor profile when relevant.
Use the same global profile while each community retains its local role, title, fields, and visibility.
Membership status, community title, join answers, moderation state, custom fields, and local visibility stay attached to the community.
Community profile edit routes use the account-level editors while keeping the member inside the community navigation context.
Empty shared sections can remain visible to their owner for editing while other viewers see only populated, permitted content.
Global Sapeans profiles and their public URLs belong to the platform identity. Some community actions—such as messaging an investor—remain available only through an existing community context and its permissions.
No. Core identity and professional sections are global. Community roles, titles, custom fields, join answers, and community-specific visibility remain local.
Yes. The profile visibility controls cover discovery, profile content, and contact information. Community-specific visibility remains separate.
The original project owner remains canonical. A linked collaborator decides whether that same read-only project appears in their portfolio and can later hide or restore it.
No. The public investor presentation avoids per-deal amounts, ownership, valuation, and returns. Public company relationships require explicit confirmation.