> For the complete documentation index, see [llms.txt](https://docs.devsolve.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devsolve.app/km/faq/reports-and-organizations.md).

# Reports និង Organizations FAQ

<details>

<summary>ហេតុអ្វីមិនអាច Submit ទៅ Program?</summary>

បញ្ជាក់ថាអ្នក Sign in, Program Active, Target In Scope ហើយ Organization បាន Approve Researcher Access ប្រសិនបើត្រូវការ។

</details>

<details>

<summary>តើអាច Edit Report ក្រោយ Submit ទេ?</summary>

Report Review Screen បច្ចុប្បន្នព្រមានថាមិនអាច Edit ក្រោយ Submit។ ពិនិត្យ Draft ជាមុន ហើយប្រើ Private Collaboration សម្រាប់ Clarification។

</details>

<details>

<summary>Duplicate និង Needs More Information បង្ហាញនៅណា?</summary>

Backend រក្សា Detailed State។ Researcher List បច្ចុប្បន្ន Group Duplicate ជាមួយ Rejected និង Needs More Information ជាមួយ Triaging ខណៈ Report Detail អាចរក្សា Raw State។

</details>

<details>

<summary>Rewards Page បង្ហាញ Real Balance ឬ?</summary>

មិនទាន់ទេ។ ទំព័រដែលបានពិនិត្យប្រើ Demonstration Records។ កុំចាត់ទុក Totals ឬ Export ជា Payment Commitment។

</details>

<details>

<summary>ហេតុអ្វីមិនអាច Invite Team Member?</summary>

Invitee ត្រូវមាន DevSolve Account ក្រោម Email នោះជាមុន។ អ្នកត្រូវមាន Authority ហើយ Existing Membership ឬ Pending Invitation អាចរារាំង Invitation ថ្មី។

</details>

<details>

<summary>Researcher Access និង Team Membership ដូចគ្នាឬ?</summary>

ទេ។ Researcher Access អនុញ្ញាត External Researcher ឱ្យ Report។ Team Membership ផ្តល់ Internal Workspace Role និង Permissions។

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devsolve.app/km/faq/reports-and-organizations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.