add Perspective limits and also Scenes and sharing#934
add Perspective limits and also Scenes and sharing#934AlexicaWright wants to merge 5 commits intoneo4j:consolefrom
Conversation
|
|
||
| Style settings for a Scene is determined by the Perspective by default. | ||
| If you change the styling, the changes only affect the current Scene and any new Scenes you create follow the Perspective styling. | ||
| If you have write permission on the Perspective, you can choose to save the styling to the Perspective. |
There was a problem hiding this comment.
If you have write permission on the Perspective
With Console shared storage, concept of read/write permissions is not applicable. We are not checking for database roles at all, and we allow all Console roles to create and edit the perspectives, even if they have a read-only (such as PROJECT_VIEWER).
This might change when sharing feature is ready, because the plan is that user can't modify shared resources. But for now there is no sharing, and user can always modify their own perspectives and scenes.
| [WARNING] | ||
| ==== | ||
| Scenes rely on node and relationship IDs in Neo4j. | ||
| Changes to this underlying data can cause data in saved Scenes to appear incorrectly if IDs are reused by the database. |
There was a problem hiding this comment.
I wonder if it's worth mentioning that if you pause and restore the instance, the user is going to lose the scene data? Might be worth discussing with Jeff.
We have a card about this, and currently there is no workaround, the user always loses scene data on pause/restore, because that changes nodes and rels elementIds.
https://linear.app/neo4j/issue/BLOOM-1035/resuming-instance-empties-the-scene
2 participants
No description provided.