View Jeli Settings

🚧

Required User Permissions

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

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

You will be presented with a Settings menu with the following options:

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

Integrations

The Integrations menu is where our inbuilt integrations can be connected and managed.

🚧

Required User Permissions

Admin permissions are required to manage integrations.

For more information, please visit our integration articles:

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

Incident Response

The Incident Response tab allows you to configure settings related to your Jeli IR Bot.

🚧

Required User Permissions

Admin permissions are required to manage incident response settings.

Here you can configure:

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

Incident Roles

Define the roles that can be assigned in the the Jeli app for Slack. 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 Slack app on incident open, and the new role commands will be available during the incident (from our example 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

❗️

Deletion Warning

This action is not reversible.

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.

Broadcast Channels

Broadcast channels help those who are not directly responding to an incident stay informed. Each channel will receive a persistent message and subsequent updates as the state of the incident changes.

1. To add default broadcast channels for your incidents, search and select your preferred channel(s) under Default broadcast channels.
2. To remove broadcast channels for your incidents, click the to the right of the channel name.

Severity

Define the severities that can be assigned in the the Jeli app for Slack. 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

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

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. Modify the type and select Update to save your changes.

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. Confirm you would like to delete this type.

Primary Jira

Configure a primary Jira issue that will be created when an incident is opened using /jeli open. The incident name will become the issue title, and the issue key will be part of the incident channel name.

Please see our Jira Integration article for more information on the integration.

Set a Default Configuration

1. Default jira project: Select the project you would like your ticket to be automatically created on.
2. Default jira issue type: Select a default issue type.

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.

1. Hover over the Default Jira project field.
2. Click the on the right to clear the input.

Opportunities

🚧

Required User Permissions

Admin permissions are required to manage opportunity settings.

Opportunity Level Access Controls

In Jeli, you have the ability to control who can view, edit, delete and manage access for every opportunity. This access can be assigned in Slack before any data is imported into Jeli, and it can then be managed through the web app after import.

Opportunity Owners

Every opportunity in Jeli must have an Opportunity Owner. You can set the owner in Slack when an incident is closed and/or a new opportunity is created. Owners have full access to the opportunity and can edit data, including deleting the opportunity itself.

Opportunity Owners can then delegate access to other users, including assigning Opportunity Owner to additional users.

📘

Admin Access

Admins for your organization automatically inherit Opportunity Owner level access to every opportunity in Jeli. You can see your list of admins for your organization here within your settings page.

Opportunity Roles & Access Levels

The following roles can be applied to individuals, or as a default level of access for an opportunity:

• No Access
  • Users that have No Access to an opportunity will not see this opportunity in the Jeli app, either in the homepage or in Learning Center.
  • Additionally, trying to navigate directly to an opportunity that a user does not have access to will present a modal indicating that the user does not have access and to contact the account admin.

• Viewer: Can’t edit or change access
  • Viewers can view a read-only version of the opportunity report, but can not view the raw data for the opportunity, or edit the report.

• Editor: Can edit, but can’t change access
  • Editors can view the Access page to see who currently has which level of access, but they can not modify current roles or add new users to the opportunity.

• Owner: Can edit and manage access
  • Owners have full permission on the opportunity.

Who can be assigned roles

Every opportunity in Jeli must have a default level of access that applies to every user in the organization.

From there, either the Opportunity Owner or account admins can assign varying levels of access to specific individuals within your organization.

As mentioned earlier, account admins automatically have Opportunity Owner levels of access to every opportunity in your account.

Managing Opportunity Access

Configure Access on Incident Close

When closing an incident in Jeli with /jeli close, or creating a new Opportunity via /jeli import, Jeli will prompt you to specify an Opportunity Owner, and a default level of access.

Templates

Templates are managed in app.jeli.io by navigating to Settings Opportunities Templates. 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.

🚧

Required User Permissions

Admin Level Permissions are required to create, edit, and delete templates.

Reach out to an Admin to make any changes to existing templates in your Jeli instance.

You can also create, edit, and delete templates from this page, in addition to the Opportunity level.

Template options

You can make templates specifically for either the Executive Summary, Takeaways, or both sections. The Markdown-supported text field makes it easy for you to transfer any existing retrospective templates over to Jeli.

📘

Use Jeli Templates

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

User Management

🚧

Required User Permissions

• Admin Level Permissions are required to manage user roles.
• In addition, Admins cannot update their own roles. Please contact another Admin if you wish to do so.
• To add someone as an admin visit User Management Settings in the Jeli App.

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

1. To update the role of a user, you can either scroll through to find them in the table of users, or search for their name via the search bar on top of the table.
2. Once you find the user you wish to edit the role for, click the Access level dropdown for their table row and select the role you want to assign.

You can also choose to filter the list of users by role by clicking on the icon on the Access level table heading.

API Tokens

🚧

Requirements

• Admin permissions are required to manage API access tokens.
• Not all Jeli pricing plans offer API access. Please see our Pricing Page for details.

Generate API Access Tokens

1. To generate an API Access Token, click Settings in the left-hand sidebar.

2. Select API Tokens, then click Generate Token in the top right.

   

3. Enter a meaningful Name for the token.

4. Make sure to Copy the access token, since the token value will only be visible to you at the time of creation.

   

Use API Access Tokens

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.

Edit API Access Tokens

The only token attribute that is editable after creation is the token name. It is not possible to edit the token value.

1. Click Edit to the right of the token.
2. Edit the token Name and then click Save.

If you’ve lost your token value, see Revoking Tokens below.

Revoke API Access Tokens

❗️

Revoking Warning

This action is not reversible.

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.

Webhooks

Webhooks allow you to receive notifications with associated data on Jeli events. 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.

🚧

Required User Permissions

Admin permissions are required to manage webhooks.

Create a Webhook

1. On the Webhooks page, click Add webhook to bring up the add webhook modal.
2. Perform 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.
2. Select the type of event you would like to send to your endpoint and then click Test again.

Edit a webhook

1. To edit, click the menu to the right of your preferred webhook and select Edit.
2. You may edit the 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 Update to save your changes. Upon updating, this will increment the version.

Delete a webhook

❗️

Deletion Warning

This action is not reversible.

1. To delete, click the menu to the right of your preferred webhook and select Delete.
2. A confirmation dialog will appear. Click Delete again to confirm.