# Share your projects
## Share projects
1\. Navigate to the **Workspaces** page.
2\. Click the dropdown menu next to the project that you want to share and click **Share**. (Note: Only the project creator and admin can see the **Share** button)
3\. Type one or more email addresses, define the [project role](#roles-and-permissions) and click **Invite**. Now, your recipients can see the project after refreshing their pages.
## Visibility settings
When you create a new project, you can choose whether to make it visible to all members of the organization. By clicking the dropdown under **"Seen by"**, you can decide who can see your resource.
* **Shared members**: Only the members who have permission to access the project can see the resource on their Resource page.
* **All members:** All members (except for the guests) in the organization can view the project and request permissions.
## Roles and Permissions
### Roles
#### :bulb:Creator
The Creator is the one who creates the project. The Creator has full privileges on the project. Each project has only one Creator.
#### :key:Admin
Admins have almost the same privileges as the Creator. However, the Admins cannot change the role of the Creator and approve the access requests from organization members. A project can have multiple Admins.
#### :pen\_fountain:Editor
Editors can modify, sync, and export the resource but cannot share it with others and change the permissions of any existing shared users.
#### :blue\_book:Viewer
Viewers can only see the project on their Workspaces page but cannot do anything with it. They have to send requests to get more permissions.
### Permissions
There are two types of permissions:
#### Share user access
It is to determine how a shared user can do for the project.
* **View**: can see the project on the Workspaces page.
* **Edit:** can rename and delete the project, and apply actions in the project.
* **Import**: can add new tables to the project.
* **Export**: can export data from any table in the project.
#### Manage asset access for user
It is to determine how a shared user can do for the project access of another shared user.
* **View:** can see the list of the users who can access the resource.
* **Edit:** can share the project with another user or change the permissions (or roles) of the existing shared users.
| Permissions | Creator | Admin | Editor | Viewer |
|---|
| Share user access | | | | |
| - View | ☑️ | ☑️ | ☑️ | ☑️ |
| - Edit | ☑️ | ☑️ | ☑️ | |
| - Import | ☑️ | ☑️ | ☑️ | |
| - Export | ☑️ | ☑️ | ☑️ | |
| Manage asset access | | | | |
| - View | ☑️ | ☑️ | | |
| - Edit | ☑️ | ☑️ | | |
### Change roles or edit permissions
You can click the **`Share`** button next to the project name and then you can see the list of the shared users. You can change the role of a team member by clicking the dropdown next to his name. (Note: only the project [Creator and Admins](#roles-and-permissions) have the privilege to edit permissions.)
### Leave the project
If you don't need to access some of the projects anymore, you can go to the Workspace page and leave the project by clicking the **Leave** button next to the project name. Once you leave the project, you cannot access the project anymore unless request permissions again. (Note: the project Creators cannot leave their projects.)
---
# Agent Instructions: 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:
```
GET https://docs.acho.io/organization/share-your-projects.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.