> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/grammarly.md).

# Grammarly

Use Grammarly data with Cortex XSIAM.

The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.

This connector includes the following capabilities and sub-capabilities (if applicable):

**SaaS Posture Configuration Monitoring:** Detect, monitor and alert on settings of your SaaS application.

**saas-posture-config-remediation:** Help remediate the misconfigured security settings of your SaaS application.

### How to configure the Grammarly connector

Cortex XSIAM accesses your Grammarly instance using Okta SSO credentials. Your organization must use Okta as an identity provider, and the Okta account must be configured for multi-factor authentication (MFA) using one-time passcodes.

To access Grammarly, Cortex XSIAM requires the following information, which you will specify during the connection process.

* **User Email:** The email address of an Okta user account. The user must have Grammarly administrator privileges. Cortex XSIAM uses this account to scan your Grammarly instance for misconfigured settings.
* **User Password:** The password for the Okta user account.
* **Okta Subdomain:** The Okta subdomain for your organization, included in the login URL that Okta assigned to your organization.
* **MFA Secret Key:** A key used to generate one-time passcodes for multi-factor authentication.

Perform the following procedures in the order that they appear below.

#### Task 1: Collect Information for Accessing Your Grammarly Instance

1. Identify the Okta user account that Cortex XSIAM will use to access your Grammarly instance. The account must have Grammarly administrator privileges.

   > Note the credentials for this account. You will provide the email address and password to Cortex XSIAM during the onboarding process.
2. Identify your Okta subdomain. The subdomain appears in the Okta login URL that your organization uses (for example, in `https://yourcompany.okta.com`, the subdomain is `yourcompany`).
3. Generate and copy an MFA secret key for the Okta user account. Store it securely in a text file.

   > Do not continue to the next step unless you have collected all four values: User Email, User Password, Okta Subdomain, and MFA Secret Key. You must provide them to Cortex XSIAM during the onboarding process.

#### Task 2: Connect Grammarly to Cortex XSIAM

1. In Cortex XSIAM, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Source** page, search for Grammarly.
4. Under **Recommended**, hover over the new Grammarly integration and click **Add Instance** to launch the configuration wizard.
5. Under the **Capabilities** tab, enter a name for your application.
6. Select **Security Posture** under **Default Capabilities**. Click **Next**.
7. Under the **Connection** tab, enter the **User Email**, **User Password**, **Okta Subdomain**, and **MFA Secret Key** details.
8. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments.
9. A confirmation message shows that Grammarly is successfully connected. Confirm the **Summary** details and click **Save instance**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/grammarly.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
