Hello,
How to restrict write access to my dashboard from any users outside my team application?
For example:
I am "User1" and I created "Test" dashboard in "App1".
App1 is my team application. I want to restrict write access (but allow read access) to "Test" dashboard from any users outside "App1"
I want to allow ONLY my team within "App1" to have read and write access to "Test" dashboard.
If I set the following setting (see below), users from outside App1 can go inside the App1 and edit the dashboard.
Please suggest. Thank you!!
Hi @LearningGuy,
you have to create a role for your team, and enable writing permission on the dashboard only for this team.
There isn't an exclusion permission, you have to define who can access and who can modify an object.
You should do the same thing for all the knowledge objects in your dashboard (fields, eventtypes, etc...).
For this reson it's always a good idea to design roles and permissions before the app creation, to avoid to modify al the object at the end of the development process.
Ciao.
Giuseppe
Hi @gcusello
If I am not an admin, Is it possible to do the following? (refer to my main question)
I want to allow ONLY my team within "App1" to have read and write access to "Test" dashboard.
Thanks
Hi @LearningGuy ,
let me know if I can help you more, or, please, accept one answer for the other people of Community.
Ciao and happy splunking
Giuseppe
P.S.: Karma Points are appreciated 😉
Hi @gcusello ,
Just to clarify. I am not an admin, so it's not possible for me to create a role , correct?
Thanks
Hi @LearningGuy,
I understand that you're not an admin, but roles is the only way to restrict accesses in Splunk.
So, ask to your administrators to creare different roles to enable your dashboards and knowledhe objects ony to selected (by roles) users.
Ciao.
Giuseppe
Hi @LearningGuy,
you have to create a role for your team, and enable writing permission on the dashboard only for this team.
There isn't an exclusion permission, you have to define who can access and who can modify an object.
You should do the same thing for all the knowledge objects in your dashboard (fields, eventtypes, etc...).
For this reson it's always a good idea to design roles and permissions before the app creation, to avoid to modify al the object at the end of the development process.
Ciao.
Giuseppe