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

📘

Availability

Jeli is available if you have a standalone Jeli plan or the Enterprise plan for Incident Management.

Contact our Sales Team to upgrade to an account plan with Jeli.

🚧

Required User Permissions

You must have admin permissions to manage Jeli settings. To add a user as an admin, visit User Access Management Settings in the Jeli web app.

View Jeli Settings

To access Jeli settings, navigate to Settings in the left navigation menu.

The following settings are available:

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

Integrations

You can manage and connect integrations in the Integrations menu. For more information, 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

In the Incident Response menu, you can configure settings related to your Jeli Slackbot. You can configure the following settings:

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

Incident Roles

Select the Incident Roles tab to define which roles you can assign in the Jeli Slackbot. You can assign these roles when you start an incident using /jeli open or update an incident during an active incident using /jeli set-<role_name>.

The default incident roles in Jeli are Incident Commander and Communications Lead. You can edit these roles to customize the name or Slack command alias, but you cannot delete them.

Add Roles

1. Click Add Role in the upper right of the configuration page.
2. Enter the information for the new role into the fields:

3. Click Add. The new role displays in your list of incident roles.

The new role shows up in the Jeli Slackbot when an incident opens, and the new role commands are available during the incident. Based on the example in the previous section, the commands are /jeli sc and /jeli set-scribe.

Edit Roles

1. Select Edit to the right of the role you want to edit.
2. Update the fields using the following guidelines:

3. Click Update to save your changes.

Delete Roles

1. Select Delete to the right of the role you want to delete.
2. In the confirmation dialog, click OK to confirm the deletion.

❗️

Deletion Warning

This action is not reversible.

Broadcast Channels

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

Add Broadcast Channels

1. Under Default broadcast channels, search and select your preferred channels to add default broadcast channels for your incidents.

Remove Broadcast Channels

1. Click to the right of the channel name to remove broadcast channels for your incidents.

Severity

Select the Severity tab to define the severities that you can assign in the Jeli Slackbot. You can assign these severities when you start an incident using /jeli open or update an incident 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 details:

3. Click OK to save the severity level.

In the following example, Severity 3 is added. You can set this in the channel using the severity modal /jeli sev or the shortcut /jeli sev minor.

Edit Severity

1. Select Edit to the right of the severity you want to edit.
2. Update the fields using the following guidelines:

3. Click Update to save your changes.
4. To change the order of your severity levels, drag and drop 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, or facilitator to update the incident status.

1. Select the Status Reminders tab.
2. Under Status reminders, configure the following options:

Types

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

Add Incident Types

1. Click Add type.
2. Enter the following information:

3. Click OK to add the incident type.

📘

Default Incident Type

The default incident type is called Default. You can modify this type, but you cannot delete it.

Edit Incident Types

1. Select Edit on the context menu for the type you want to edit.
2. Update the fields using the following guidelines:

3. Click OK.

Delete Incident Types

❗️

Deletion Warning

• Deleting incident types does not remove the type from existing incidents. Because of this, you cannot reuse incident type names.
• You cannot delete types that a workflow is actively using.

1. Select Delete on the context menu for the type you want to delete.
2. In the confirmation modal, click Delete.

Primary Jira Issue

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

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

All Primary Jira Issues

In the All Primary Jira Issues section, select the checkbox if you want 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 values for the following fields:

3. Optional: Map Jeli incident stages to Jira issue statuses by selecting corresponding statuses in the dropdowns to associate Jeli incident stages with Jira issue statuses.

4. Click Save configuration.

Remove Default Configuration

1. To disable the automatic creation of Jira tickets for incident response, select Remove on this page.

Opportunities

In the Opportunities menu, you can configure Tag Types and Templates.

Tag Types

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

Templates

Select the Templates tab to manage templates in your Jeli account. You can view all templates currently used in your Jeli instance, who created each template, and whether a template is set as a default template.

📘

Use Jeli Templates

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

Create a Template

1. Click Create Template.
2. Enter the following details:

3. Click OK.

Edit a Template

1. Select Edit to the right of the template you want to edit.
2. Update the fields and click OK.

Delete a Template

1. Select Delete to the right of the template you want to delete.
2. In the confirmation modal, click Remove.

User Management

🚧

Required User Permissions

Jeli admins cannot update their own roles. Contact another admin user to update your role.

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 for their name in the search bar.
2. Click the Access level dropdown to the right of the user's name and select the role you want to assign.

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

API Tokens

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

Use tokens as Bearer tokens in the header of your API requests. To generate and run authenticated API requests, visit our API documentation.

📘

Availability

Not all Jeli pricing plans offer API access. 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 to store it in a safe place. The token value is only visible once.
4. Click Copy and close. This action copies the access token to your clipboard if you did not copy it in the previous step.

Edit an API Access Token

You can edit the name of an API access token after creation. You cannot edit the token value.

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

Revoke an API Access Token

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

1. Click Revoke to the right of the token.
2. In the confirmation dialog, click Revoke token.

❗️

Irreversible Action

This action is not reversible, and you cannot recover a deleted API access token.

Webhooks

Webhooks allow you to receive notifications with event-specific data when actions occur in Jeli. For example, if you want updates 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, fill out the following fields:

3. Click Add to create the webhook.

Once created, your webhook displays in a paginated list that shows the endpoint URL, the description, the enabled status, and an autoincrementing version number.

📘

Unable to Roll Back

You cannot roll back to previous versions.

Test a Webhook

1. Click the menu to the right of your preferred webhook and select Test.

📘

Note

If the Test option is grayed out, ensure that the webhook is enabled.

2. Select an event type and click Test.

The following example shows 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. Select Edit next to your preferred webhook.
2. Make your required changes and click Update.

After you save, the webhook version increments by one.

Delete a Webhook

1. Select Delete to the right of your desired webhook.
2. In the confirmation dialog, click Delete endpoint.

❗️

Deletion Warning

This action is not reversible, and you cannot recover deleted webhooks.

Import Log

The Import Log provides an audit log of Slack and other integration data imports.

📘

Availability

Import logs are available with the Professional, Business, and Enterprise for Incident Management pricing plans.

Contact our Sales Team to upgrade to a plan featuring Jeli.

The information provided includes:

To download a CSV of the import log data, click Download CSV in the upper right.