Skip to main content
Portfolio projects give people something concrete to inspect on your profile. A product can be published by a builder or by a company, and it can credit other contributors without handing them control of the listing.

​
Publish your own project

  1. Select Publish, then choose whether the listing belongs to your proof page or to a company hub.
  2. Add the product name, summary, description, category, stage, ecosystems, links, and media.
  3. Add contributors under Team Members by searching for their name or username. Add only people who actually worked on it.
  4. Submit the listing and review its public product page.
Adding someone does not credit them immediately. Each person receives a request and the listing shows them publicly only after they approve it.

​
Respond to a team-credit request

Open the Portfolio tab on your profile and look for Team requests. Approve a request if you worked on that project and it will appear in your portfolio, or reject it if the association is wrong. The person who added you is notified of your decision. Pending and rejected requests are never public credit.

​
What team access covers

Being on a product team controls collaboration on that product only. It does not prove employment at the associated company, does not carry a verified experience badge, and does not transfer ownership of your profile or of the listing. After shipping, update the project status, working links, networks, and your contribution. A repository, product page, demo, contract, or public milestone gives reviewers something to inspect.

​
Continue on Dapping

Browse or publish products

Open products to publish a project you shipped or to answer a pending team-credit request.

Why experience verification can reset, be rejected, or be revoked

See why changing a role or its evidence can remove an existing verification.

Add skills and endorse another builder

Keep your skill list focused and endorse work you have seen firsthand.
Last modified on September 12, 2026