> For the complete documentation index, see [llms.txt](https://docs.potlock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.potlock.io/user-guides/soon-personas/observor.md). # Observor An observor is someone who is just observing and is not logged in. This is different than a non-kyc'd donor who is someone with an account without the I-Am-Human face verification NFT. ## Actions Things an observor can do * Browse: Browse available projects * Audit: Considering everything is on chain, you don't need to be logged in to see, * Transaction History Page: What you can't do * Contribute to funding rounds * Make attestations * Make direct donations or get on chain referrals {% hint style="info" %} It is important to note that most observors from a UI persepctive have similar views, but certain dashboard buttons are not showing, or things like donate show an popup message prompting the observor to do an action to get a role. For example if you try to donate it says you must be logged in. {% endhint %} * Matched Rounds * Have Access to Round Manager Dashboard * Attest for a Project * Literally any interaction on chain, log-in bro its how you do things --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.potlock.io/user-guides/soon-personas/observor.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.