Business Stakeholder - what would that user see?

Colleen1
Tera Contributor

We have a requirement to enable our end users to see, read only, incidents and requests.  I was told that could be accomplished with the new 'Business Stakeholder' role in New York and beyond.  Before we purchase new licenses for this role, we would simply like to see screenshots of what a Business Stakeholder user would see if they wanted to see an incident, a request, and a change.  I even asked our SN rep and they said to reach out to the community?  So, we are on Madrid and will be going to Orlando next month.  We cannot ask our customer if they want us to purchase something if we cannot show them what value that new role would provide us.  Could someone possibly supply demo data screenshot as they impersonate a Business Stakeholder user please?  And any additional details /benefits of having this new role for end users.  Thank you in advance.  

1 ACCEPTED SOLUTION

Jeff Currier
ServiceNow Employee
ServiceNow Employee

It looks pretty much the same except everything is read only.  You can switch views and all.  But cannot change anything except approvals.

find_real_file.png

View solution in original post

4 REPLIES 4

Jeff Currier
ServiceNow Employee
ServiceNow Employee

It looks pretty much the same except everything is read only.  You can switch views and all.  But cannot change anything except approvals.

find_real_file.png

This would be a good use case for you to test things out in a personal developer instance.

The business stakeholder role contains other roles which in turn contain other roles.  In my environment, I ended up with 28 roles by just adding business stakeholder.  In your real environment, you could have subsets of those for your actual business stakeholders so they don't see as much.

Thank you Jeff!  I greatly appreciate this information and I am new to the personal developer instance and will look into this.

Just a heads up, we just enabled the Business Stakeholder license, they can see most things, however, they do not have access to Requests. Why they did this, do not know.  We had to work with Support to verify this and we verified the docs are incorrect, as the docs for the sn_request_read role only give read access to records the users is an approver on.