[MGNLDEMO-334] travel-demo-publisher has read/write access to website Created: 16/Mar/20 Updated: 16/Mar/20 |
|
| Status: | Open |
| Project: | Magnolia Demo Projects |
| Component/s: | magnolia-travels |
| Affects Version/s: | 1.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Low |
| Reporter: | Richard Gange | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
For demonstration reasons it would be better if the travel-demo-publisher had only read access to the website workspace. This is how it used to be in earlier versions. Otherwise there is really not much distinction between eric and peter. You want to be able to show how the write restriction is handled in content apps. |