Content
View differences
Updated by Wieland Lindenthal 8 months ago
**As** a project admin
**I want** want to** the existing permissions for user groups for documents to continue working
**so that** I can maintain the same level of control
**Acceptance criteria**
* If a user opens a document they either get a 'show/readonly' view or an edit view - based on their permissions
* Permissions
* view\_documents (project level)
* index
* show
* download attachments
* manage documents (project level), includes all above and level)
* new
* create and
* edit
* update
* destroy
* add attachments
* destroy attachments
**Technical notes**
* The permissions already exist, we need to make sure to enforce them - especially 'show' in 'view\_documents' will need to be handled as the default view is 'edit'. BlockNote can be set to read-only readonly mode - see [https://www.blocknotejs.org/docs/reference/editor/overview#editable](https://www.blocknotejs.org/docs/reference/editor/overview#editable)
**I want**
**so that** I can maintain the same level of control
**Acceptance criteria**
* If a user opens a document they either get a 'show/readonly' view or an edit view - based on their permissions
* Permissions
* view\_documents (project level)
* index
* show
* download attachments
* manage documents (project level), includes all above and
*
*
*
*
*
* add attachments
* destroy attachments
**Technical notes**
* The permissions already exist, we need to make sure to enforce them - especially 'show' in 'view\_documents' will need to be handled as the default view is 'edit'. BlockNote can be set to read-only