> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/a-c-integrations/akamai-guardicore-segmentation-formerly-guardicore-centra-setup-for-workbench.md).
# Akamai Guardicore Segmentation (formerly Guardicore Centra) Setup for Workbench
## Step 1: Enable Console Access for Expel
Having read-only access to the interface of your technology allows Expel to dig deeper during incident investigations. Our device health team uses this access to investigate potential health issues with your tech. For more information, see [Why Expel Asks for Console Access](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md).
1. Log in to Guardicore Segmentation Centra and navigate to **Administration > User Management > Users** and then click **+ Add User**.
2. Complete the fields as follows:
* **Username** - type Expel.
* **Email Address** - leave blank.
* **Description** (optional) - leave blank or enter a description of your choice.
* **Permission Scheme** - select **Administrator**.
* Create a Temporary Password.
* Do **NOT** select **Enable 2-Step Verification**.
* Do **NOT** select **Enable user to view passwords used in security incidents**.
3. Click **Save**.
4. Log in to Guardicore Segmentation Centra using the user credentials you just created and set a **new** **Password**. Make a note of the new password for later use.
## Step 2: Add Akamai Guardicore Segmentation as a Security Device in Workbench
Now that you have the correct access configured and noted the credentials, you can integrate your tech with Workbench.
1. [Log in to Workbench](https://workbench.expel.io/settings/security-devices?setupIntegration=guardicore).
2. Fill in these fields:
* **Name** - type "Expel API Access".
* **Location** - type the geographic location of the server (or "cloud" for cloud servers).
* **Server** - type the server URL address.
* **Username** - type the username you created in [Step 1](#uuid-ae54a985-4522-7442-3bc2-c702f654e9e3_bridgehead-25687).
* **Password** - type the new (not temporary) password you created in [Step 1](#uuid-ae54a985-4522-7442-3bc2-c702f654e9e3_bridgehead-25687).
3. Click **Save**.
Your device should be created successfully within a few seconds. A few reminders:
* After your connection is healthy, it will take some time for your device to begin polling and receiving data.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* Polling will happen first; data will be received after that. **You must refresh the page to see updates.**
* If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, [contact our support team for help](/support/how-to-reach-us.md).
* To check if alerts are coming through, navigate to **Dashboards > Alert Analysis**. Scroll to the device you want to check, and select the **Expel Alerts** tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we [tune your device](/workbench-reference/alerts/how-expel-alerts-work.md#device-tuning).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.expel.io/connect-your-technology/a-c-integrations/akamai-guardicore-segmentation-formerly-guardicore-centra-setup-for-workbench.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.