Entities and relationships

Understand how builders, company hubs, products, listings, and public relationships fit together on Dapping.

Each entity has its own public identity, and the relationships between them do not all carry the same weight. Reading one as though it were another is the usual mistake.

Core entities

Entity	Represents	Public context it carries
Builder profile	One person and their professional identity	Experience, projects, skills, recommendations, intentions, connected accounts, and selected wallets
Company hub	An organization or ecosystem	Official details, team, products, listings, events, and company activity
Product	A shipped product or project	Description, category, ecosystem, team credit, reviews, deployments, and token context
Listing	A job, grant, bounty, hackathon, accelerator, event calendar, or event	Publisher, audience, eligibility, dates, location, rewards or compensation, and destination
Conversation	A direct or group conversation between accepted participants	Message-request state, participants, roles, and invite access

A product is published either by a company hub or by an individual builder. That choice decides who can edit it and whose name appears on it.

Relationships between entities

Relationship	Between	How it is established
Experience	Builder and company	Entered by the builder, then optionally verified
Company membership	Builder and company	Invitation accepted; owner, admin, or member
Product team credit	Builder and product	Offered or requested, then accepted by the other party
Recommendation	Builder and builder	Written by one profile about another
Skill endorsement	Builder and builder	One endorsement per person per skill
Follow	Builder and builder, or builder and company	One-directional; no acceptance required
Publisher	Builder or company, and listing	Chosen at publish time

Public interactions and where they apply

Interactions are not available everywhere. The surfaces differ by type, and the differences are deliberate.

Interaction	Where it is available
Review	Products only. One review per person per product, rated 1 to 5, editable at any time
Comment	Jobs, grants, bounties, accelerators, hackathons, and events. Not on products, companies, event calendars, or profiles
Upvote	Products, jobs, grants, bounties, accelerators, hackathons, event calendars, events, and blog posts
Going	Event calendars, events, and hackathons
Follow	Builder profiles and company hubs

You cannot review a company, a job, or an event. You cannot comment on a product or a company hub.

Relationships are not interchangeable

• Verified experience is stronger evidence than a self-entered role, and it is evidence about one role only.
• Accepted team credit connects a builder to a product. It does not establish which parts they built.
• Company access is a workspace permission. It is not a public employment claim, and a public team listing is not a permission.
• Following, Going, upvotes, reviews, and comments record activity or opinion. They verify nothing.

Evaluate the entity itself and the evidence attached to the specific claim. A relationship elsewhere on the platform is context, not a guarantee.

Related guides

Personal profiles and company hubs are different

Choose the correct identity for personal work and company operations.

Roles and permissions

Compare company, product team, and group conversation roles.