> For the complete documentation index, see [llms.txt](https://docs.neoncloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neoncloud.com/get-started/projects-and-rbac.md).
# Projects & RBAC
Organize resources with **projects** and control access with **roles**.
Click on "Create New Project" and enter **project name, project description, and project purpose.** Then click on "Create Project" and the new project will be created.
This is your default project homepage where you can see all active services within that project, view/add/remove users in the project, and see the resource quota assigned to the project.
## Projects vs. Account
* **Account:** Your identity, billing, and security context
* **Project:** Isolation boundary for resources, quotas, and RBAC
## Users
Navigate to **Profile** → **Users** and you can create/modify/delete users here and assign them to projects.
## Roles & Permissions (RBAC)
Navigate to **Profile** → **Roles** and you can create new roles, modify/delete existing ones, and assign these roles and permissions to users.
When adding a new role, you can choose specific services, features, and permissions you want to assign to users in this role.
These are typical roles and permissions you can assign to you team members. *Please note these are suggestions and may vary based on industry, team size, use case, etc.*
| Role | Scope | Permissions |
| ------------------ | --------------- | ----------------------------------- |
| Owner | Project | Full control, manage roles/quotas |
| Contributor | Project | Create/update/delete most resources |
| Viewer | Project | Read-only access |
| Billing (optional) | Account/Project | Invoices, transactions |
## Best practices ✅
* Least-privilege roles; **Viewer** by default
* Separate **billing** from **ops** access
* Review **members** quarterly and rotate credentials
---
# 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.neoncloud.com/get-started/projects-and-rbac.md?ask=&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.
