Hello leo82,
Thank you for your question.
1. I tested this by creating two test accounts, one with the Data Designer role and one with Designer.
The Data Designer could create and share a Notebook. The Designer could view the Notebook the Data Designer shared with them, but not edit it or create a new Notebook.
2. We recommend using Users or Groups to limit access to specific data cubes, not Roles. To allow or restrict certain rows of data to a specific user or group of users, you can set the default data security behavior for each table and then define when the rule applies. Here is our documentation for that. https://docs.sisense.com/main/SisenseLinux/data-access-security.htm?Highlight=group%20data%20security
I hope that helps. Please let us know if you have any more questions.
Have a great day!
Hi DRay
Thanks for your reply.
I'm a 'Data Designer' but can't create a Jupyter Notebook in E1. We use the on prem version L2023.6.0.260. Does this version allow 'Data Designers' to create new Notebooks? How can I fix this? Thoughts?
To clarify, I'm talking about using Jupyter Notebook for Python code in ElastiCube builds, as explained here: https://docs.sisense.com/main/SisenseLinux/transforming-data-with-custom-code.htm.
The page says admins need to enable this feature. So, is the process: 1) Admin enables Custom Code, 2) Assigns 'Data Designer' role to a user, 3) Then 'Data Designer' role can create new 'Notebook' and work with Jupyter Notebooks in ElastiCube builds?
