Set document to readonly when a user is not allowed to create / update #18076

madsrasmussen · 2025-01-22T14:12:21Z

This PR ensures that the document workspace set to readonly if a user doesn't have permissions to create or update.

This PR updates the document workspace context to check for create and update permissions. The workspace now correctly behaves for a user with

browse: The UI is readonly. The user can't access the save button.
create: The user can create a document but it becomes readonly after creation is done.
update: The user can only edit already created documents.

Permissions

Language Permissions

…t-allowed-to-save

madsrasmussen added 22 commits January 22, 2025 09:45

split manifest file

25ea4c4

use const

8d5ad2d

use const

c0cfcf1

use const

5f2da9c

require permission to create or update to render save action

8c0b19e

require permission to update to render "save and preview"

7182562

require permission to update + publish to render "save and publish"

a195780

keep button as it is extendable

be59fda

keep buttons as they are extendable

52ec596

set readonly state based on user permission

cb538a4

render readonly tag for invariant documents

75e03c1

remove double array

f0ee29a

return permitted state in callback

aa70431

disable save button if all variants are read only

cf95080

Merge branch 'v15/dev' into v15/bugfix/document-readonly-when-user-no…

1cc0570

…t-allowed-to-save

rename private method

45c7ef7

split check on create vs update

54dd49e

clear state when resetting the state

b35321c

add null check

0ae2ccd

remove unused

e272518

Update document-user-permission.condition.ts

f579a75

change translation to browse

60afa2b

Provide feedback