Ask Alex
Ask Alex is an assistant inside Identiguard. It can see the page you are on and answers questions about it in plain language, using the workspace’s own data.
| Where | The Alex button near the bottom of the sidebar, and the Ask Alex AI buttons on events and incidents |
| Who can use it | Admins, members and viewers. Each user authorises it for their own account. |
| Needs | MCP & AI agent access on in the workspace’s Policies, and a plan that includes AI access. See Plans and billing. |
| Screen | Desktop-width windows only |
Alex is read-only. It cannot dismiss events, close incidents or change settings.
Open it
Section titled “Open it”Choose Alex in the sidebar, above the Plan card. The panel opens on the right of the page. The button then reads Close Alex.
The panel header shows:
- the name Alex,
- a New conversation icon,
- an X (Close panel),
- a line “Viewing:
<page>” that names the page Alex can see, for example “Viewing: Identity event feed” or “Viewing: Incident detail”. Pages without a specific description read “Viewing: Workspace page”.
Drag the left edge of the panel to change its width. Double-click the edge to return to the default width. The width is not remembered after you reload the page.
Authorise it
Section titled “Authorise it”Like any AI application, Alex needs your permission before it can read a workspace. You give permission once for each workspace.
- Open the panel. It reads “Checking Ask Alex authorization…” for a moment.
- Under the heading Authorize Ask Alex, choose the Authorize Ask Alex button.
- A consent page opens. Under It will be able to: read what Alex can do. Under For these workspaces: tick the workspaces to include. The workspace you came from is already ticked.
- Choose Authorize 1 workspace (the label shows the number you ticked). To cancel, choose Deny.
- You return to the page you were on, with the panel open.
Things to know:
- The permission is for you only. Each user authorises Alex for their own account.
- The permission lists workspaces. If you open Alex in a workspace that you did not tick, you see Authorize Ask Alex again.
- You can remove the permission at any time. See Switch it off.
Instead of the Authorize Ask Alex card you may see one of these messages. Each is explained in Troubleshooting.
- “AI access is turned off for your account”
- “AI access is disabled for this workspace”
- “Ask Alex is unavailable right now”
Ways to start a question
Section titled “Ways to start a question”| Where | Button | What it sends |
|---|---|---|
| Sidebar | Alex | Nothing. It opens the panel so that you can type. |
| An event row in the feed, beside View | Ask Alex AI | “Explain the <platform> event “<event type>” on tenant <tenant> at <time>. What happened, does it represent a risk in this workspace, and what should we do next?” |
| The top of an incident page | Ask Alex AI | “Explain incident <id>. What happened, why did it open, how was its score arrived at, and what should we do next?” |
| A card in What fired on an incident, for a detector | Ask Alex AI | “Explain why the detector “<name>” fired on incident <id>. What rule did it match, which events did it group, and does it represent a real risk here?” |
| A card in What fired, for a baseline anomaly | Ask Alex AI | The same question, for “the baseline anomaly “<name>”” |
The Ask Alex AI buttons open the panel if it is closed, attach the event or incident, and send the question for you. Follow-up questions in the same conversation stay about that item while you remain on the page.
If Alex is still answering, or still checking your authorisation, the question waits and is sent afterwards.
There is no Ask Alex AI button inside the Event Details dialog, and none on the Correlations page. On those, open the panel from the sidebar and type your question.
Starter prompts
Section titled “Starter prompts”Before your first question, the panel greets you with “Hello <first name>. Ask me about anything you can see in this workspace - I can see the page you’re on.” Under Try asking it offers three prompts. Select one to send it.
| Page | Prompts |
|---|---|
| Dashboard | “Summarise this workspace”, “Any issues I should look at?”, “What should I do next?” |
| Events | “Summarise the events on this page”, “Any unusual event activity?”, “What should I investigate first?” |
| Tenants pages | “Summarise the tenants shown here”, “Any tenants that need attention?”, “What should I do next?” |
| A status page | “Summarise the current Okta status”, “Any incidents I should know about?”, “What should I do next?” |
| An advisories page | “Summarise these Okta advisories”, “Which advisory matters most here?”, “What should I do next?” |
| Every other page | “Summarise this page”, “Anything I should investigate?”, “What should I do next?” |
“Every other page” includes Incidents, an incident page, Correlations, Journeys, the reporting pages and all settings pages. There is no starter prompt that is specific to incidents.
Chat controls
Section titled “Chat controls”| Control | What it does |
|---|---|
| Input box, “Ask Alex about this page…” | Type a question of up to 10,000 characters. |
Enter |
Sends the question. Shift+Enter starts a new line. |
| Ask Alex | Sends the question. |
| Copy answer | An icon that appears when you hover over an answer. It copies the answer. |
View <page> |
Links under an answer. They open the pages the data came from, such as the dashboard, events, Incidents, Correlations, tenants, reporting or an advisories page. |
“Context <tokens> / 262k tokens (<n>%)” |
Shows how much of Alex’s memory the conversation uses. It turns amber from 60% and red from 80%. |
| Compact | Replaces the whole conversation with one summary message that starts “Summary of the conversation so far.” You cannot undo it. Alex does this by itself at 80%. |
| New chat, or the New conversation icon | Clears the conversation. |
| Retry | Appears after an error. It sends the same question again. |
The conversation is kept while you move between pages of the same workspace. It is lost when you switch workspace, reload the page or close the panel. Nothing is stored.
What it can do
Section titled “What it can do”- Read events, including the raw payload.
- Read an incident, its score and its evidence.
- Explain the rule behind a detector or a baseline anomaly.
- Read tenant health, provider status and advisories.
- Read vendor documentation and status pages from an approved list.
- Read another web page, if you allow it. See below.
When Alex asks to read a web page
Section titled “When Alex asks to read a web page”Alex sometimes wants to open a page that is not on the approved list. The answer then shows a box with the web address and two buttons.
| Button | Result |
|---|---|
| Fetch this page | Alex asks the same question again, with that one address allowed. |
| Don’t fetch | The box reads “Not fetched. Alex did not open this page.” |
If you ask something else without choosing, the old box reads “Not fetched.”
Alex only opens https addresses, and at most 3 approved addresses for one question. Check the address before you allow it.
Limits
Section titled “Limits”| Limit | Value |
|---|---|
| Questions | 10 for each user in one minute. A question that needs several data lookups counts more than once. |
| Data lookups | 60 for each user in one minute. This is shared with any MCP client you use. |
| Lookup rounds for one question | 8 |
| Question length | 10,000 characters |
| Conversation length | 24 turns. After that, the oldest turns are no longer sent with your question. |
When you pass the question limit, the panel shows “Unable to answer right now.” with Retry. Wait one minute.
Switch it off
Section titled “Switch it off”For yourself, for one application. Open the account menu and choose AI & MCP access. Under Authorized applications, find Ask Alex and select the bin icon beside it. The panel shows Authorize Ask Alex again. This takes effect at once in the same browser and within about a minute elsewhere.
For yourself, completely. On the same page, switch off Allow MCP clients to access my account. This also blocks every MCP client for your account.
For the whole workspace. A workspace admin opens Policies, goes to the AI & MCP access section and switches off MCP & AI agent access. This turns off Alex and MCP clients for everyone in the workspace.
See Your account and Settings.
In a demo
Section titled “In a demo”Alex works best on an incident. Choose Ask Alex AI at the top of the incident, then ask it to explain the incident in two sentences for a manager. Check the answer before you rely on it in front of a client, as with any AI assistant.
Authorise Alex before the demo, and use a desktop-width window.
Troubleshooting
Section titled “Troubleshooting”Opening and authorising
Section titled “Opening and authorising”| What you see | Why | What to do |
|---|---|---|
| The Alex button is missing, or Ask Alex AI does nothing | The window is narrower than a desktop screen. | Widen the window, or use a desktop. |
| “Checking Ask Alex authorization…” does not go away | The check is slow. | Wait a few seconds, then reload the page. |
| Authorize Ask Alex | You have not authorised Alex, you removed the permission, or this workspace was not ticked. | Choose Authorize Ask Alex, tick the workspace and approve. |
| “AI access is turned off for your account” and “Re-enable it under Account > AI & MCP access to use Ask Alex.” | You switched off Allow MCP clients to access my account. | Open the account menu, choose AI & MCP access and switch it on. |
| “AI access is disabled for this workspace” and “A workspace admin has turned off MCP & AI agent access in the workspace policies.” | The workspace policy is off, or the plan does not include AI access. | An admin switches on MCP & AI agent access under Policies. |
| “Ask Alex is unavailable right now” and “The assistant service can’t be reached. Try again shortly.” | The assistant service cannot be reached. This also appears when the workspace is paused for billing. | Try again shortly. Ask an admin to check billing. If it continues, tell the product team. |
While you chat
Section titled “While you chat”| What you see | Why | What to do |
|---|---|---|
| “Unable to answer right now.” with Retry | The question failed. Common causes: more than 10 questions in a minute, a question over 10,000 characters, a network drop, or a fault in the assistant service. If your permission was removed, the panel changes to Authorize Ask Alex. | Wait 60 seconds and choose Retry. Shorten the question. If it continues, choose New chat. |
| “No response received.” as the answer | The answer ended with no text. | Ask again. |
| “Could not summarise the conversation.” | Compact failed. | Choose Compact again, or New chat. |
| “This chat is at 24 turns - the oldest are no longer sent with your question. Compact it or start a new chat to keep Alex’s full attention.” | The conversation reached 24 turns. | Choose Compact or New chat. |
| The Context line is amber or red | The conversation uses 60% or 80% of Alex’s memory. At 80% Alex compacts it. | Expected. Choose Compact or New chat when you change subject. |
| “Unable to copy to clipboard.” | The browser blocked the copy. | Select the text and copy it by hand. |
| “Not fetched. Alex did not open this page.” or “Not fetched.” | You chose Don’t fetch, or you asked something else before you chose. | Ask again and choose Fetch this page if you trust the page. |
| The conversation is gone | You reloaded the page, closed the panel or switched workspace. | Conversations are not stored. Copy an answer you need with Copy answer. |
For other problems, see Troubleshooting.