> ## Documentation Index > Fetch the complete documentation index at: https://docs.dapp.ing/llms.txt > Use this file to discover all available pages before exploring further. # Use Company Activity to track work and follow up > Review company engagement and published-listing performance, then follow up from the source. Company Activity combines engagement around your company with performance for published listings. Use it to see what deserves a response and which work is attracting attention. Roles, invitations, and ownership are managed separately in **Role Management**. ## Read the Activity feed 1. Select the company you manage and open **Company Hub → Activity**. 2. Choose a time range and filter for engagement, comments, reviews, proof, claims, listings, or follows. 3. Open the person, company, or listing connected to an activity. 4. Respond or follow up from the source when an activity needs attention. Use the feed to understand recent context behind your engagement totals, not as a permissions log. ## Review published performance Switch to **Published** to review jobs, grants, bounties, hackathons, accelerators, events, side events, and dApps published by the company. Filter by listing type, compare visible views and interactions, and open the exact listing before deciding what to change. ## Record participation attestations The **Participation attestations** tab lets a verified company vouch for people who took part in a campaign it organized. Only active, verified companies can issue them; until the company is verified, the tab explains that rather than offering the import. 1. Choose one of the company's own events, hackathons, or grants. 2. Choose the outcome to assert, **Participant** or **Winner**. 3. Upload a CSV of Dapping profiles, preview how each row will be treated, then publish. The preview separates new attestations, promotions from participant to winner, rows already attested, repeats within the file, and profiles with no Dapping account, so nothing is published blind. An attestation is a company assertion, not a Dapping verification, and it does not change a builder's self-declared **Going** status. It becomes ecosystem evidence for your company straight away, but it stays off the builder's public profile until that builder chooses **Show on profile**. A builder can also report an issue, which marks the attestation disputed and leaves it out of your attestation totals until it is resolved. Removals and dispute decisions keep an audit history. ## Useful operating habits * Respond to useful comments and reviews while their context is current. * Check listings with views but little interaction for unclear audience, timing, terms, or destination links. * Review engagement after a product launch, hiring campaign, event, or ecosystem program. * Open the public item before editing it so you understand what visitors currently see. If the workspace is missing, confirm that the correct company is selected and that your role still grants access. A recent role change may require a refresh. Do not put internal candidate, applicant, or private company information into public listing fields. Company Activity is not a complete audit trail, an applicant tracker, or a guarantee of audience quality. ## Continue on Dapping Open Company Activity to see recent engagement and which published listings need follow-up. ## Related guides Invite teammates, choose their access, and transfer company ownership. See the difference between company access, a listed role, and verified experience. Build a focused talent shortlist from profile proof, current intentions, and visible match context.