> For the complete documentation index, see [llms.txt](https://docs.kaana.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaana.com/product/getting-started/understanding-your-role.md).

# Understanding Your Role

Kaana uses role-based access control (RBAC) to determine what you can see and do within the platform.

## Standard Roles

### Owner

The highest level of access within an organization.

* Full access to all features and data
* Can manage billing and subscription
* Can add and remove administrators
* Can configure organization settings

### Admin

Administrative access for managing the organization.

* Create, edit, and delete projects
* Manage users and assign roles
* Configure integrations and settings
* Access all reports and analytics
* Cannot modify billing (unless also Owner)

### Member

Standard access for team members.

* View projects they're assigned to
* Create and update tasks
* Upload and view documents
* Log activities and comments
* Limited access to sensitive settings

### Guest

Read-only access for external collaborators.

* View projects they're invited to
* View documents and activities
* Cannot create or modify content
* Limited navigation access

## What Can You Do?

Your role determines access across different areas:

| Feature          | Owner | Admin | Member | Guest |
| ---------------- | ----: | ----: | -----: | ----: |
| View Dashboard   |   Yes |   Yes |    Yes |   Yes |
| Create Projects  |   Yes |   Yes |   Some |    No |
| Edit Projects    |   Yes |   Yes |    Own |    No |
| Delete Projects  |   Yes |   Yes |     No |    No |
| Upload Documents |   Yes |   Yes |    Yes |    No |
| Log Activities   |   Yes |   Yes |    Yes |    No |
| Create Issues    |   Yes |   Yes |    Yes |    No |
| Manage Users     |   Yes |   Yes |     No |    No |
| View Reports     |   Yes |   Yes |   Some |    No |
| Change Settings  |   Yes |   Yes |     No |    No |
| Manage Billing   |   Yes |    No |     No |    No |

## Ownership-Based Access

Some features use ownership-based permissions:

* "Own" items — Content you created or are assigned to
* "All" items — Any content in your organization

For example, a Member might be able to edit their own tasks but not tasks created by others.

## Checking Your Permissions

{% stepper %}
{% step %}

### Open Settings

Go to Settings > Profile.
{% endstep %}

{% step %}

### View Your Role

Your role is displayed on your profile page.
{% endstep %}

{% step %}

### Check Navigation

Navigation shows only features you can access.\
If you need additional access, contact your administrator.
{% endstep %}
{% endstepper %}

## Why Can't I See Something?

If a feature or menu item is missing:

* Your role may not have access to that feature
* The feature may be disabled for your organization
* You may need to be added to specific projects

Contact your administrator if you believe you should have access to something.

## Custom Roles

Your organization may have custom roles with specific permission combinations. Check with your administrator to understand any custom roles in use.


---

# 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.kaana.com/product/getting-started/understanding-your-role.md?ask=<question>&goal=<endgoal>
```

`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.