Javi – Omada AI assistant

Javi is an AI-powered assistant that can help you with a variety of identity and access management activities. It complements Omada Identity, allowing expedite handling of access requests and approvals. You can ask Javi any question about Omada (this includes detailed technical questions related to documentation and processes). Multiple languages are supported. Javi is an optional paid feature.

Core features and functionalities

You can ask Javi to perform the following actions:

• access request - submit and manage access requests with ease
• access approval - approve access requests directly within Microsoft Teams
• Q&A - get answers to questions about Omada Identity and technical documentation
• scheduled notifications - use scheduled notifications for pending approval requests

Installing Javi in Microsoft Teams

Prerequisites: You need to have the Teams administrator permissions to onboard a new application.

1. Go to Teams admin center. Select Teams apps > Manage apps.

   

2. In the top right corner, click Actions > Upload new app.

3. Navigate to the Javi AI Assistant .zip file provided by Omada. Click Open.

4. Wait until the app is installed. Once the installation is complete, locate the app on the list:

   

5. Click the app for additional configuration options. In the Users and groups tab, you can configure the app availability. Change this setting to make it available to specific users or groups, and then review installation requests. To make Javi available by default, see Setup policies in Microsoft Teams documentation for details.

   

Best practices

1. State your intent at the beginning. Avoid adding any further details at first. "I want to request access", "Show me my pending approvals" should be sufficient.

2. Avoid ambiguities. For example, you have just requested to see your pending approvals. You then ask to review further five most recent items from the list. Finally, you enter Give me more info on the first 3. Javi will be confused about the first 3 resources - whether they refer to the first or the second overview.

3. Maintain relevance to the most recent turn. For example, you are requesting access to a resource. Javi has gathered your business context and selected resources, and is now asking you for the reason. Instead of providing the reason, you respond I want access to resource [a second resource] to carry out a project. Javi may be confused over which action to perform next.

4. Avoid abrupt shifts of scope. For example, you are in the process of making an access request. You have asked Javi to help you select a business context for your request. If you ask Javi at that point What are the approval requests pending to that context?, Javi will most likely be confused.

5. Use the search or find keywords. If Javi is having trouble retrieving information (such as your pending approvals, resources for requesting access, resource ids for requesting access, your business contexts etc.) use the keywords.

6. Paraphrase your prompt. When Javi is not returning the desired response, try asking in a different way using alternative phrasing.

7. Be conscious of memory capacity when requesting access. Avoid requesting access to more than 2 (possibly 3) resources per request. Maintain a step-by-step, fast conversation flow when filling in the requirements for the access request:

   1. Select context.
   2. Find resource_A.
   3. Find resource_B.
   4. State the reason.
   5. Confirm the summary.
   6. Make a request.

8. Avoid overloading your prompt. Your prompt should focus on performing a single step. For example, if you want to request access to multiple resources during an access request, search for them one by one using one turn per resource search.