Docs » Splunk On-Call user roles and permissions » Stakeholder role

Stakeholder role 🔗

During a major incident, it is often necessary to keep internal stakeholders up to speed while allowing incident responders to work on the problem without distraction. The Stakeholder role allows teams to send paging notifications to Stakeholders with notifications to specific incidents.

For detailed role information, see Splunk On-Call user roles and permissions.

Adding a Stakeholder to Splunk On-Call 🔗

Stakeholders are a limited user role and cannot take actions within the platform. Stakeholder users can receive paging notifications and have limited access to the On-Call platform. Although all users can receive stakeholder messages, only stakeholder users are offered a discount, with access to the incident Stakeholder timeline and user profile.

Please contact Splunk On-Call Support to enable this feature in your account and your sales representative or Splunk On-Call Billing to purchase stakeholder licenses.

Sending a Stakeholder Message 🔗

In Splunk On-Call, you may send messages to Stakeholders and Users from the incident UI and the API. Messages may be sent to individual users or teams via SMS or Email notification.

Within an incident you can send a message to stakeholders.

To POST updates on incidents to your Stakeholder users via the API, see the sendMessage call found in the API documentation .

Stakeholders Notifications 🔗

Stakeholders can receive notifications via SMS or email depending on the preference set in individual user profiles. These messages include a link to the web interface and Stakeholder message history.

Stakeholder Experience 🔗

Stakeholders may follow a notification link to see incident-specific updates. They may also choose their preferred method of notification.

Stakeholders can view incident updates. Stakeholders can choose their preferred notification methods in their profile.

This page was last updated on Aug 01, 2024.