> 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/organizations/teams-and-permissions.md).

# ក្រុម តួនាទី និងសិទ្ធិ

Role ពណ៌នាពីភារកិច្ចទូទៅរបស់ Team Member។ Explicit Permissions កំណត់ថា Company Workspace Tools ណាខ្លះដែលបង្ហាញ។ Organization Owner គ្រប់គ្រងទាំងពីរតាម **Team Management**។

## Roles

Invitation Form មាន **Manager**, **Member**, **Viewer**។ Role ជ្រើស Default Permissions និងកំណត់ Permission Ceiling ហើយ Saved Permission Set កំណត់ Tools ដែលអាចប្រើ។

| Role        | Default Access                                               | Maximum Access                                                                                          |
| ----------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------- |
| **Manager** | Programs, Reports, Disclosure, Rewards និង Researcher Access | Permissions ទាំងអស់ដែល Invitation Form ផ្តល់ រួមទាំង Program Deletion                                   |
| **Member**  | View Programs; View និង Triage Reports                       | Program/Report Work, Disclosure និង Rewards; មិនមាន Program-state, Deletion ឬ Researcher-access Control |
| **Viewer**  | View Programs                                                | View Programs និង Reports ប៉ុណ្ណោះ                                                                      |

| ផ្នែក              | Permissions                                                                                 |
| ------------------ | ------------------------------------------------------------------------------------------- |
| Programs           | `VIEW_PROGRAMS`, `CREATE_PROGRAM`, `EDIT_PROGRAM`, `MANAGE_PROGRAM_STATE`, `DELETE_PROGRAM` |
| Reports            | `VIEW_REPORTS`, `TRIAGE_REPORTS`                                                            |
| Disclosure/Rewards | `MANAGE_DISCLOSURE`, `AWARD_REWARDS`                                                        |
| Researcher Access  | `MANAGE_RESEARCHERS`                                                                        |

`MANAGE_MEMBERS` មានក្នុង Frontend Permission Type ប៉ុន្តែមិនបង្ហាញក្នុង Invitation Form បច្ចុប្បន្ន និងមិនត្រូវបានប្រើដើម្បីបើក Team Management ទេ។ កុំចាត់ទុកវាជា User-facing Access។ Team Management បច្ចុប្បន្នជា Owner-only។

## បន្តទៅ Workflow

* [អញ្ជើញសមាជិក](/km/organizations/invite-members.md)
* [គ្រប់គ្រងក្រុម](/km/organizations/manage-team.md)
* [ប្រើ My Team និងប្ដូរ Workspace](/km/organizations/my-team-and-workspaces.md)
* [ទទួលយកការអញ្ជើញ](/km/account/invitations.md)

ក្នុង Team Management Roster, Invitation ដែលមិនទាន់ Accepted បង្ហាញជា **Invited** ទោះបី Underlying Member Status អាចជា `SUSPENDED` ក៏ដោយ។ នេះជា Invitation State មិនមែន Active Member ឬ Organization Suspension ទេ។


---

# 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/organizations/teams-and-permissions.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.