> ## 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. # Verify your team and attest work > Confirm the roles people hold at your company, keep your People tab accurate, and treat honest attestation as an asset. Only your company can confirm that someone works there. That makes the attestations you issue an asset: your people carry them for the rest of their careers, and other companies read them when weighing a claim. ## How a request reaches you A builder adds a role at your company and asks you to attest it. The request lands in **Employee Verification Requests** inside Role Management, where any owner or admin approves or rejects it. Each request tells you what approval will do, because the consequences differ: an approved current role lists the person on your public **People** tab, while an approved past role records employment proof without changing the tab. Builders can also verify a role through a work email on your domain, which is reviewed by Dapping. A company attestation remains the stronger, more direct signal. ## What your approval creates An attested role at a verified company gives the builder a verified experience badge, counts toward their profile verification, and feeds their Karma through independent proof. It also keeps working for you: an attested current role is labeled as attested on your People tab, distinct from someone who merely accepted an invitation, and a company whose roles are attested reads very differently to candidates and partners than one where nothing is confirmed. Every attestation you issue is read later by someone deciding whether to trust that builder, so your company's name travels with it. That is what makes attesting carefully worth something. If your company is not verified yet, you can still attest an employment role; the badge simply waits until [verification](/for-companies/set-up-a-hub-that-earns-trust) completes. Participation attestations are the exception: issuing those needs a verified company, because they borrow your identity's weight. ## Attest honestly, revoke cleanly Approve what you can actually confirm: the person, the title, the dates. When a role ends or was recorded wrongly, revoke the attestation; the People listing goes with it, and the builder is told why. If a builder edits the proof-bearing fields on a verified role, the verification is revoked rather than silently carried over, and they must ask again, so an attestation never covers a claim you did not review. An attestation you approve for yourself at your own company is labeled self-attested and does not carry the weight of independent proof, which is what protects the value of every attestation you issue. ## Beyond employment Employment is one kind of attestation. For hackathons, grants, events, and campaigns, the same principle scales through [participation attestations](/for-companies/attest-participation-at-scale), issued in bulk to everyone who took part. ## Keep proof and access separate Attesting a role gives someone proof they can carry for the rest of their career. It never gives them access to your hub: workspace permissions are managed separately through [roles and invitations](/help/companies/manage-company-roles-invitations-and-ownership), and the two are deliberately unconnected so that confirming a fact is never a security decision. What you are confirming is a working relationship with someone you know, not their identity to the world and not a performance reference. [How proof works](/for-companies/the-proof-model) is the full accounting. ## Continue on Dapping Open your company hub's Role Management to answer verification requests. ## Related guides The four signals around a role and exactly what approval changes. Invite teammates, choose their access, and transfer company ownership. Issue attestations for campaigns, hackathons, and events in bulk.