# Project Permissions Project permissions define who can access and interact with a project, including its chat, timeline, and tasks. {% hint style="warning" %} Core members with access to a project automatically gains access to view its content - tasks, views, chat, etc. {% endhint %} ## Project Types

| Project: | Accessible by: | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Private | Only invited members have access. | | Public to Group | All group members would have access to the project. (Note: Inherited users would have the same permission as the group member, please check the image below) | | Public to Anyone | This project is available as a template to members outside of the organization (*Currently not available for general consumption*) | {% hint style="info" %} A guest user if invited to a project would be able to access tasks, chat and timeline of the project. {% endhint %} ## Project user roles ### Administrator Has full control over the project, including the ability to edit permissions and manage settings. * [Invite a member](/project.md#users-tab) / remove members * Assign admin roles * Change project type * [Duplicate or move project](/project.md#duplicate-project) * [Delete Project](/project.md#delete-project) * Modify project due date and description * Add the project to portfolios ### Editor These users would be able to create, modify and delete tasks within a project. But edit users can't modify the project permissions or change the project settings, due date or description. ### Commenter These users would only be able to comment on tasks. Incase a task is assigned to a comment only user they would be able to change the assignee or mark the task complete. ### Viewer These users can only access the project but not make any modifications. ## Permission Overview in a Table The table below outlines the capabilities of project members with Project admin, Editor, Viewer and Commenter permissions. Commenters can also be assigned tasks, which gives them some additional permissions on those specific tasks.

Action	Project Admin	Editor	Commeter	Commenter with task assigned	Viewer	Viewer with task assigned
Delete or archive project	✅	❌	❌	❌	❌	❌
Rename project	✅	❌	❌	❌	❌	❌
Change project privacy or team	✅	❌	❌	❌	❌	❌
Move project to a different group	✅	❌	❌	❌	❌	❌
Customize permissions	✅	❌	❌	❌	❌	❌
Add or modify project overview	✅	✅	❌	❌	❌	❌
Add or modify project description	✅	✅	❌	❌	❌	❌
Share project and manage memberships	✅	✅	❌	❌	❌	❌
Add and modify tasks, including subtasks, dependencies, and multihoming	✅	✅	❌	❌	❌	❌
Change project appearance such as default view, icon and color for everyone	✅	✅	❌	❌	❌	❌
Add and modify workflow features such as custom fields, forms, task templates, bundles, autoshifting due dates, and integrations	✅	✅	❌	❌	❌	❌
Complete tasks	✅	✅	❌	✅	❌	✅
Change assignee	✅	✅	❌	✅	❌	✅
Change due date	✅	✅	❌	❌	❌	❌
Set project status	✅	✅	❌	❌	❌	❌
Create a discussion post	✅	✅	✅	✅	✅	✅
Submit forms	✅	✅	✅	✅	✅	✅
Modify custom field values	✅	✅	❌	❌	❌	❌
Log time	✅	✅	✅	✅	❌	✅
Add attachments	✅	✅	✅	✅	❌	✅
Remove attachments	✅	✅	❌ Can only remove their own attachments	❌ Can only remove their own attachments	❌	❌ Can only remove their own attachments
Comment on tasks or messages	✅	✅	✅	✅	❌	✅

--- # 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://guide.smarttask.io/permissions/project-permissions.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.