Jeli administrators can manage Jeli settings, integrations, and user permissions within the platform, ensuring your team has the necessary tools and access to manage incidents effectively and maintain a streamlined, secure operational environment.

🚧

Required User Permissions

Admin permissions are required to manage Jeli settings. To add someone as an admin, visit User Access Management Settings in the Jeli App.

View Jeli Settings

To access Jeli settings, click Settings in the left navigation.

You can now access the following a settings options:

• Integrations
• Incident Response
• Opportunities
• User Management
• API Tokens
• Webhooks

Integrations

The Integrations menu is where you can manage and connect integrations. For more information, please visit our integration articles:

• Slack Integration | Jeli
• PagerDuty Integration | Jeli
• Opsgenie Integration | Jeli
• Zoom Integration | Jeli
• Jira Integration | Jeli
• Import HR Data
• Google Meet Integration | Jeli
• Statuspage Integration | Jeli
• Okta Integration | Jeli
• Vanta Integration | Jeli
• ServiceNow Integration | Jeli
• Nobl9 Integration | Jeli

Incident Response

The Incident Response menu allows you to configure settings related to your Jeli Slackbot. Here you can configure:

• Incident Roles
• Broadcast Channels
• Severity
• Status Reminders
• Types
• Primary Jira

Incident Roles

Select the Incident Roles tab to define which roles can be assigned in the the Jeli Slackbot. These roles can be assigned when an incident is started using /jeli open or updated during an active incident using /jeli set-<role_name>.

The default Incident Roles in Jeli are Incident Commander and Communications Lead. These roles can be edited to customize the name or Slack command alias, but cannot be deleted.

Add Roles

1. Click Add Role in the upper right of the configuration page.
2. Enter the following:
   1. Incident role name: The name that will be displayed in the list of role options.
   2. Slack command alias: The alias responders can use in the incident channel to assign the role.
   3. Role help message: The help message that will be sent to the user when they are assigned to the role.
3. Click Add and you will see the new role displayed in your list of Incident Roles

This new role will now show up in the Jeli Slackbot when an incident opens, and the new role commands will be available during the incident. Based on the example from the image above, the commands would be/jeli sc, /jeli set-scribe.

Edit Roles

1. Select the menu to the right of the role you would like to edit, and select Edit.
2. You may edit the following:
   1. Incident role name: The name that will be displayed in the list of role options.
   2. Slack command alias: The alias responders can use in the incident channel to assign the role.
   3. Role help message: The help message that will be sent to the user when they are assigned to the role.
3. Click Update to save your changes.

Delete Roles

1. Select the menu to the right of the role you would like to edit, and select Delete.
2. A confirmation dialog will appear. Click OK to confirm deletion.

❗️

Deletion Warning

This action is not reversible.

Broadcast Channels

Select the Broadcast Channels tab to configure how stakeholders will stay informed during incident response. Each broadcast channel will receive a persistent message and subsequent updates as the incident state changes.

Add Broadcast Channels

To add default broadcast channels for your incidents, search and select your preferred channel(s) under Default broadcast channels.

Remove Broadcast Channels

To remove broadcast channels for your incidents, click to the right of the channel name.

Severity

Select the Severity tab to define the severities that can be assigned in the the Jeli Slackbot. These severities can be assigned when an incident is started using /jeli open or updated during an active incident using /jeli sev.

Add Severity

1. Click Add Severity in the upper right of the configuration page.
2. Enter the following:
   1. Severity name: The name that will be displayed in the list of severity level options.
   2. Slack command: The Slack command shortcut that will come after /jeli sev. Example: /jeli sev critical.
   3. Description: The description that will appear in the severity dropdown.
3. Click OK to save the severity level.

In the below example we are adding Severity 3, which can be set in the channel either by the severity modal /jeli sev or the shortcut /jeli sev minor.

Edit Severity

1. Select the menu to the right of the severity you would like to edit, and select Edit.
2. Edit the following:
   1. Severity name: The name that will be displayed in the list of severity level options.
   2. Slack command: The Slack command shortcut that will come after /jeli sev. Example: /jeli sev critical.
   3. Description: The description that will appear in the severity dropdown.
3. Click Update to save your changes.
4. The order of your severity levels can also be changed by dragging and dropping a severity level to a new position in the list.

Status Reminders

Select the Status Reminders tab to configure the frequency and methods used to remind the Incident Commander/Lead/Facilitator to update the incident status.

1. Under Status reminders, select the following:
   1. Remind me every: Select the time frequency from the dropdown.
   2. How would you like the Incident Commander to be reminded?: Select the contact method from the dropdown.

Types

Select the Types tab to configure incident types, which allow you to activate specific actions using workflows during your response. Incident types also assist with sorting and filtering incidents, and trend analysis when looking at a specific incident.

Add Incident Types

Configure any incident type your team needs.

1. Click Add type.
2. Enter a Name and short Description of the incident type to help users know when it applies.
3. Click OK to add the incident type.

📘

Default Incident Type

The default Incident Type is called Default. This type can be modified, but not deleted.

Edit Incident Types

1. Select the context menu for the type you would like to edit, and select Edit.
2. Make your required changes to the Name and/or Description, and click OK.

Delete Incident Types

❗️

Deletion Warning

• Deleting incident types does not remove the type from existing incidents. Because of this, you are not able to reuse incident type names. Keep this in mind when deleting types.
• Types that are actively being used by a workflow cannot be deleted.

1. Select the context menu for the type you would like to edit, and select Delete.
2. In the confirmation modal, click Delete.

Primary Jira Issue

Select the Primary Jira Issue tab to configure the Jira issue that will be created when you open an incident using /jeli open. The incident name will become the issue title, and the issue key will be part of the incident channel name.

Please read Jira Integration | Jeli for more information about setting up the initial integration.

All Primary Jira Issues

In the section All Primary Jira Issues, select the checkbox if you'd like to create a Jira comment for every Jeli Slackbot status update.

Set a Default Configuration

1. Click Configure Primary Jira Issue.
2. In the modal, select a Default Jira project and Default Jira issue type.

3. Optional: Map Jeli incident stages to Jira issue statuses. Make selections in the dropdown to associate Jeli incident stages with Jira issue statuses.

4. Click Save configuration.

Remove Default Configuration

If you would like to disable the automatic creation of Jira tickets for incident response, you may clear the configuration on this page by selecting Remove.

Opportunities

The Opportunities menu allows you to configure Tag Types and Templates.

Tag Types

Select the Tag Type tab to see an overview of the Opportunity Tags in your account. Here you can create a new tag type and configure auto-tagging.

Templates

Select the Templates tab to manage templates in your Jeli account. This is where you can view all templates currently used in your Jeli instance, who created the template, and if the template is used as a default template.

📘

Use Jeli Templates

To learn more, see Use Templates for Incident Reviews in Jeli.

Create a Template

1. With the Templates tab selected, click Create Template.
2. Enter the following:
   1. A Name for the template.
   2. Template: The template's content. Github-flavored Markdown is supported.
   3. Type: Select Summary, Takeaways or Both Summary and Takeaways (default)
   4. Set as default for Summary: Toggle on or off.
   5. Set as default for Takeaways: Toggle on or off.
3. Click OK.

Edit a Template

1. With the Templates tab selected, select Edit to the right of the template you'd like to edit.
2. Make your required changes and click OK.

Delete a Template

1. With the Templates tab selected, select Delete to the right of the template you'd like to delete.
2. In the confirmation modal, click Remove.

User Management

🚧

Required User Permissions

Jeli Admins cannot update their own roles. Please contact another Admin user if you wish to do so.

The User Management menu is where you can edit the roles of Jeli users within your organization.

1. To update a user's role, scroll the users table or search their name in search bar.
2. Click the Access level dropdown to the right of your desired user's name and select the role you want to assign.

To narrow results by role, you can click the icon in the Access level table heading.

API Tokens

Select Settings API Tokens in the Jeli web app to manage API access keys. You can see when each token was generated and by whom.

Tokens should be used as Bearer tokens in the header of your API requests. To generate and run authenticated API requests, please visit our API documentation.

📘

Availability

Not all Jeli pricing plans offer API access. Please see our Pricing Page for details.

Generate an API Access Token

1. On the API Tokens page, click Generate token in the top right.
2. Enter a Name for the token.
3. Optional: Click to copy the access token to your clipboard for storage in a safe place, since the token's value is only visible once.
4. Click Copy and close. This will also copy the access token to your clipboard if you did not do so in the previous step.

Edit an API Access Token

You can edit an API access token's name after creation. It is not possible to edit the token's value.

1. Click Edit to the right of the token.
2. Edit the token's Name.
3. Click Save.

Revoke an API Access Token

You may revoke a token at any time. Once revoked, API requests using this token will fail.

1. Click Revoke to the right of the token.
2. A confirmation dialog will appear. Click Revoke token to confirm.

❗️

Irreversible Action

This action is not reversible, and a deleted API access token cannot be recovered.

Webhooks

Webhooks allow you to receive notifications with event-specific data when actions occur in Jeli. For example, if you want to be updated when a new opportunity is created or when an incident updates, you can use webhooks to send notifications.

Create a Webhook

1. In the Jeli web app, navigate to Settings Webhooks and click Add webhook.
2. In the modal window, enter the following:
   1. Webhook URL: Enter the URL of the destination that events are sent to.
   2. Description: A short summary describing the webhook.
   3. Enabled upon creation?: Check or uncheck this option to toggle the webhook on/off.
   4. Event Type Filtering: Select which events you wish to receive from Jeli. If no event types are checked, this webhook will receive every event.
3. Click Add to create the webhook.

Once created, your webhook will be displayed in a paginated list, along with where the endpoint events are directed to, the description, whether it’s enabled or not, and an autoincrementing number to keep track of which version you’re currently on.

📘

Unable to Roll Back

It is not currently possible to roll back to previous versions.

Test a Webhook

1. To test a webhook without opening an incident, click the menu to the right of your preferred webhook and select Test.
   1. Note: If the Test option is grayed out, please make sure the webhook is enabled.
2. Select an event type and click Test.

The following example is from a test incident.created webhook event:

{
  "incidentId": 1780,
  "name": "sparkling-base",
  "severity": "sev3",
  "slackChannelId": "C123ABC",
  "slackTeamId": "T123ABC",
  "stage": "Investigating",
  "status": "We're looking into the errors",
  "summary": "No summary set"
}

Edit a webhook

1. To edit a webhook, next to your preferred webhook select Edit.
2. Make your required changes and click Update.

After saving, the webhook's version will increment (i.e., go up by one).

Delete a webhook

1. To delete a webhook, to the right of your desired webhook select Delete.
2. In the confirmation dialog, click Delete endpoint.

❗️

Deletion Warning

This action is not reversible, and a deleted webhooks cannot be recovered.