mintlify · mintlify · Jun 23, 2026 · Jun 23, 2026
diff --git a/automations/create.mdx b/automations/create.mdx
@@ -20,12 +20,12 @@
 
 1. Open the [Automations](https://app.mintlify.com/products/automations) page in your dashboard.
 2. Click **Create a custom automation**.
-3. Configure the automation name, trigger, instructions, context repositories, integrations, and update mode.
+3. Configure the automation name, trigger, instructions, context repositories, integrations, and update mode. For details on each field, see [Configurations](/automations/manage#configurations).
 4. Click **Create automation**.
 
 ## Write effective instructions

 Effective automation instructions focus on a single task and define a clear, verifiable outcome. Automations have some variance because agents are nondeterministic, but well-formatted instructions produce more consistent results.

 - **Describe the outcome.** Tell the agent what a successful run should look like.
 - **Write a procedure.** Give the agent a step-by-step guide to follow.

diff --git a/automations/index.mdx b/automations/index.mdx
@@ -1,12 +1,12 @@
 ---
 title: "Automations overview"
 sidebarTitle: "Overview"
 description: "Automate content maintenance with Mintlify automations. Run the agent on a schedule or in response to GitHub and GitLab repository pushes."
 keywords: ["automation", "automate", "cron", "agent", "automations"]
 boost: 5
 ---

 Automations run the agent automatically on a schedule or in response to changes in a repository. Each automation defines a prompt for the agent and a trigger for when to run it. Automations support both GitHub and GitLab repositories.

 When an automation runs, the agent reads your project content and any connected repositories, then follows the prompt to make updates.

@@ -18,17 +18,19 @@

 ## Trigger types

 Automations support three trigger types.

 - **Content update**: Runs when content changes push to your Mintlify project repository, including pull request merges and direct pushes.
 - **Code change**: Runs when a pull request merges in a connected source code repository.
 - **Custom schedule**: Runs on a recurring schedule. Automations queue within 10 minutes of the scheduled time.

 Each automation has exactly one trigger. You cannot combine trigger types in a single automation.
 
 ## Usage limits
 
-Automation runs count toward your credit usage. See your credit usage, set overages, and manage your credit package on the [Usage](https://app.mintlify.com/settings/organization/usage) page of your dashboard.
+Automation runs count toward your credit usage. The credits a single run consumes depend on the size of the task: how much content the agent reads, how many files it changes, and how long the run takes. Larger context repositories and broader prompts use more credits than narrowly scoped ones.
+
+See your credit usage, set overages, and manage your credit package on the [Usage](https://app.mintlify.com/settings/organization/usage) page of your dashboard.
 
 Each automation can run up to 500 times per day. Runs that fail do not count toward this limit.
 

diff --git a/automations/manage.mdx b/automations/manage.mdx
@@ -43,7 +43,7 @@

 - **Content update**: Runs whenever you push content to your project repository, including pull request merges and direct pushes.
 - **Code change**: Runs when a pull request merges in a connected source code repository. You must specify at least one source repository.
 - **Custom schedule**: Runs on a recurring schedule you define. Automations queue within 10 minutes of the scheduled time.

 ### Update mode

@@ -112,6 +112,15 @@
 
 When you re-enable a scheduled automation or change its schedule, Mintlify recalculates the next run time from the current time. Disabled automations do not retain a pending run time.
 
+## Run an automation manually
+
+You can trigger any enabled automation on demand without waiting for its next scheduled or event-based run.
+
+1. Open the [Automations](https://app.mintlify.com/products/automations) page in your dashboard.
+2. Click the <Icon icon="play" /> run button beside the automation you want to start.
+
+Manual runs use the automation's current configuration, count toward your credit usage, and appear in the run history alongside scheduled runs.
+
 ## View run history
 
 Each automation keeps a log of past runs, including the status and a summary of changes made.
@@ -122,3 +131,13 @@
     <img src="/images/workflows/workflow-runs-light.png" alt="Automation runs page showing the automation and status filters." className="block dark:hidden" />
     <img src="/images/workflows/workflow-runs-dark.png" alt="Automation runs page showing the automation and status filters." className="hidden dark:block" />
     </Frame>
+
+Each run shows one of the following statuses:
+
+- **Queued**: The run is waiting to start. Scheduled runs queue within 10 minutes of the scheduled time.
+- **In progress**: The agent is actively working on the run.
+- **Succeeded**: The agent finished the run. If the automation made changes, the run links to the resulting commit or pull request.
+- **Failed**: The agent could not complete the run. Failed runs do not count toward your daily run limit.
+- **No changes**: The agent finished the run but did not find anything to update.
+
+Click an individual run to see its prompt, the files it read or changed, and any pull request it opened.
diff --git a/automations/reference.mdx b/automations/reference.mdx
@@ -6,6 +6,22 @@
 
 Mintlify includes predefined automations for the most common documentation maintenance tasks. Each automation has a base prompt and a default configuration. You can customize the trigger, update mode, and instructions from the [Automations](https://app.mintlify.com/products/automations) page in your dashboard.
 
+## At a glance
+
+| Automation | Default trigger | Default update mode | Context repos | Required configuration |
+| ---------- | --------------- | ------------------- | ------------- | ---------------------- |
+| Update from code changes | Custom schedule (twice weekly) | Pull request | Supported | At least one source code repository |
+| Draft changelog | Custom schedule | Pull request | Supported | None |
+| Draft improvements from assistant conversations | Custom schedule | Pull request | Not supported | None |
+| Draft improvements from user feedback | Custom schedule | Pull request | Not supported | Feedback collection enabled |
+| Translate content | Content update | Direct merge | Not supported | At least one target language |
+| Fix broken links | Content update | Pull request | Not supported | None |
+| Audit SEO metadata | Content update | Pull request | Not supported | None |
+| Fix grammar & typos | Content update | Pull request | Not supported | None |
+| Apply style guide | Content update | Pull request | Not supported | None |
+
+All defaults can be changed from the automation's settings panel. See [Configurations](/automations/manage#configurations) for the available options.
+
 ## Self-updating content automations
 
 Self-updating content automations make updates based on context that you define so your content remains accurate and up to date.

diff --git a/dashboard/sso.mdx b/dashboard/sso.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Single sign-on (SSO)"
 description: "Set up single sign-on with SAML or OIDC identity providers like Okta, Azure AD, and Google Workspace for secure team authentication."
 keywords: ["SSO", "SAML authentication", "Okta integration", "Microsoft Entra", "identity provider", "JIT", "provisioning", "OIDC"]
 ---

@@ -98,6 +98,46 @@
 
 To enable JIT provisioning, you must have SSO enabled. Navigate to the [Single Sign-On](https://app.mintlify.com/settings/organization/sso) page in your dashboard, set up SSO, and then enable JIT provisioning.
 
+## Enforce SSO-only sign-in
+
+Org owners can require everyone in the organization to sign in through your identity provider. When SSO enforcement is on, Mintlify rejects password, magic link, and Google OAuth sign-ins for org members.
+
+1. Navigate to the [Single Sign-On](https://app.mintlify.com/settings/organization/sso) page in your dashboard.
+2. Confirm that SSO is configured and verified end-to-end.
+3. Toggle **Enforce SSO-only sign-in** on.
+
+<Warning>
+  Mintlify blocks SSO enforcement if turning it on would lock every owner out of the organization. Configure at least one breakglass email or confirm an owner can sign in through your IdP before enforcing.
+</Warning>
+
+To stop enforcing SSO, toggle the setting off. Other sign-in methods become available again immediately.
+
+## Verified domains
+
+Add domains your organization owns so Mintlify can tie sign-ins and invitations back to a trusted identity. You can add up to five verified domains per organization.
+
+1. Navigate to the [Single Sign-On](https://app.mintlify.com/settings/organization/sso) page in your dashboard.
+2. In the **Verified domains** section, click **Add domain**.
+3. Enter the domain (for example, `example.com`) and click **Add**.
+4. Mintlify generates a verification token. Add it as a DNS TXT record on the domain.
+5. Return to the dashboard and click **Verify**. The status changes from **Pending** to **Verified** once the record propagates.
+
+To remove a domain, click the <Icon icon="trash" /> delete button beside it.
+
+## Breakglass emails
+
+Designate emergency-access accounts that can sign in even when SSO enforcement is on or your identity provider is unreachable. Use breakglass emails to recover access if your IdP has an outage or a misconfiguration locks members out.
+
+1. Navigate to the [Single Sign-On](https://app.mintlify.com/settings/organization/sso) page in your dashboard.
+2. In the **Breakglass emails** section, add the email addresses of the org members who should retain non-SSO access.
+3. Click **Save changes**.
+
+<Tip>
+  Use breakglass emails for owner accounts that are not tied to your primary IdP, store the credentials in a secure password manager, and review the list whenever team membership changes.
+</Tip>
+
+Each breakglass email must already belong to a member of your organization. Members listed as breakglass can sign in with a password, magic link, or Google OAuth even when SSO enforcement is on.
+
 ## Map RBAC roles with SAML groups
 
 Assign [roles](/dashboard/roles) to users based on their identity provider group membership. When a user signs in through SSO, Mintlify reads the `groups` attribute from the SAML assertion and maps those groups to dashboard roles.
@@ -163,7 +203,7 @@

 For providers other than Microsoft Entra or Okta SAML, [contact us](mailto:support@mintlify.com) to configure SSO.

 ### Google Workspace with SAML

 <Steps>
  <Step title="Create an application">
@@ -176,7 +216,7 @@
  <Step title="Send us your IdP information">
    Copy the provided SSO URL, Entity ID, and x509 certificate and send it to the Mintlify team.
    <Frame>
      ![Screenshot of the Google Workspace SAML application page with the SSO URL, Entity ID, and x509 certificate highlighted. The specific values for each of these are blurred out.](/images/gsuite-saml-metadata.png)
    </Frame>
  </Step>
  <Step title="Configure integration">
@@ -206,7 +246,7 @@

 <Steps>
  <Step title="Create an application">
    In Okta, under **Applications**, create a new app integration using OIDC. Choose the **Web Application** application type.
  </Step>
  <Step title="Configure integration">
    Select the authorization code grant type and enter the Redirect URI provided by Mintlify.

diff --git a/deploy/authentication-setup.mdx b/deploy/authentication-setup.mdx
@@ -16,7 +16,7 @@

 Authentication requires users to log in before accessing your content.

 You can configure full authentication for all pages or partial authentication where some pages are public and others are protected.

 ## Configure authentication

@@ -104,8 +104,8 @@
      * **Scopes** (optional): Permissions to request. Copy the **entire** scope string (for example, for a scope like `provider.users.docs`, copy the complete `provider.users.docs`). Use multiple scopes if you need different access levels.
      * **Additional authorization parameters** (optional): Additional query parameters to add to the initial authorization request.
      * **Token URL**: Your OAuth token exchange endpoint.
      * **Info API URL** (optional): Endpoint on your server that Mintlify calls to retrieve user info. Required for group-based access control. If omitted, the OAuth flow only verifies identity.
      * **Logout URL** (optional): The native logout URL for your OAuth provider. When users log out, Mintlify validates the logout redirect against this configured URL for security. The redirect only succeeds if it exactly matches the configured `logoutUrl`. If you do not configure a logout URL, users redirect to `/login`. Mintlify redirects users with a `GET` request and does not append query parameters, so include any parameters (for example, `returnTo`) directly in the URL.
      * **Redirect URL** (optional): The URL to redirect users to after authentication.
    5. Click **Save changes**.

@@ -137,7 +137,7 @@
 - **Scopes**: `['provider.users.docs']`
 - **Token URL**: `https://auth.foo.com/exchange`
 - **Info API URL**: `https://api.foo.com/docs/user-info`
 - **Logout URL**: `https://auth.foo.com/logout?returnTo=https%3A%2F%2Fdocs.foo.com`

 **Create a user info endpoint** at `api.foo.com/docs/user-info`, which requires an OAuth access token with the `provider.users.docs` scope, and returns:

@@ -467,7 +467,7 @@
 | [llms.txt and llms-full.txt](/ai/llmstxt) | Full support | Available behind authentication, so AI tools may not be able to access the files | Publicly accessible, reflecting public pages only |
 | [MCP server](/ai/model-context-protocol) | Full support | Requires authentication to connect | Available without authentication for public pages and with authentication for protected pages |
 | [Markdown export](/ai/markdown-export) | Full support | Full support, respects user groups | Full support, respects user groups |
-| [PDF export](/optimize/pdf-exports) | Full support | Not supported | Not supported |
+| [PDF export](/optimize/pdf-exports) | Full support | Full support, respects user groups. Authenticated pages export with images and assets included. | Full support, respects user groups. Authenticated pages export with images and assets included. |
 | [Search](/assistant/index) | Full support | Full support, respects user groups | Full support, respects user groups |
 | [Assistant](/assistant/index) | Full support | Full support, respects user groups | Full support, respects user groups |
 | [skill.md](/ai/skillmd) | Full support | Not supported | Not supported |

diff --git a/editor/branching-and-publishing.mdx b/editor/branching-and-publishing.mdx
@@ -136,6 +136,17 @@
 
 Click any changed file in the publish menu to open it in diff view and compare your branch against the published version. In visual mode you see a visual diff. In source mode you see a text diff. Files that can't display a diff, such as images or deleted files, appear in the list but aren't clickable.
 
+Changed pages are highlighted in the file tree so you can see at a glance which files an [automation](/automations) or teammate touched. Unlisted pages that appear in the branch diff are also openable from the publish menu, even though they don't appear in your site navigation.
+
+### Open an automation run in the editor
+
+When an [automation](/automations) opens a pull request, you can jump straight from the run review UI or its Slack notification into the editor on the automation's branch:
+
+- From the **Automation Runs** page in your dashboard, click **Open in editor** on a completed run.
+- From a Slack notification, click the **View changes** link.
+
+Either entry point opens the editor on the automation's branch with the changed pages preselected in the publish menu, so you can review the diff and merge or request changes without leaving the editor.
+
 ### Simultaneous publishing
 
 Only one publish can happen at a time per branch. If another team member publishes to the same branch, wait for the current publish to complete before trying again.
@@ -152,13 +163,13 @@

 ## Collaborate in real time

 When multiple people open the same page on the same branch, they edit together in real time. Each person's cursor and edits are visible to everyone, with avatars shown in the toolbar.

 - Changes from all collaborators merge automatically. Two people editing the same section won't create conflicts.
 - Undo only affects your own edits.
 - If you lose your connection, edits save locally and sync when you reconnect.

 When the [Mintlify agent](/agent) edits a page through the API or MCP, it appears in the editor like any other collaborator. You see the agent's avatar in the toolbar and a live cursor at its most recent edit location. The cursor clears automatically after the agent finishes.

 ## Git sync


diff --git a/es/automations/create.mdx b/es/automations/create.mdx
@@ -24,7 +24,7 @@ import GitlabAutomationSetup from '/snippets/es/gitlab-automation-setup.mdx';
 
 1. Abre la página [Automatizaciones](https://app.mintlify.com/products/automations) en tu dashboard.
 2. Haz clic en **Create a custom automation**.
-3. Configura el nombre de la automatización, el activador, las instrucciones, los repositorios de contexto, las integraciones y el modo de actualización.
+3. Configura el nombre de la automatización, el activador, las instrucciones, los repositorios de contexto, las integraciones y el modo de actualización. Para más detalles sobre cada campo, consulta [Configuraciones](/es/automations/manage#configurations).
 4. Haz clic en **Create automation**.
 
 <div id="write-effective-instructions">

diff --git a/es/automations/index.mdx b/es/automations/index.mdx
@@ -32,7 +32,9 @@ Cada automatización tiene exactamente un activador. No puedes combinar tipos de
 ## Límites de uso
 </div>
 
-Las ejecuciones de automatizaciones cuentan para el uso de tus créditos. Consulta tu uso de créditos, configura los excedentes y gestiona tu paquete de créditos en la página [Uso](https://app.mintlify.com/settings/organization/usage) de tu dashboard.
+Las ejecuciones de automatizaciones cuentan para el uso de tus créditos. Los créditos que consume una sola ejecución dependen del tamaño de la tarea: cuánto contenido lee el agente, cuántos archivos modifica y cuánto tarda la ejecución. Los repositorios de contexto más grandes y los prompts más amplios consumen más créditos que los que tienen un alcance acotado.
+
+Consulta tu uso de créditos, configura los excedentes y gestiona tu paquete de créditos en la página [Uso](https://app.mintlify.com/settings/organization/usage) de tu dashboard.
 
 Cada automatización puede ejecutarse hasta 500 veces al día. Las ejecuciones que fallan no cuentan para este límite.
 

diff --git a/es/automations/manage.mdx b/es/automations/manage.mdx
@@ -134,6 +134,17 @@ Puedes añadir idiomas de destino en cualquier momento abriendo la configuració
 
 Cuando vuelves a activar una automatización programada o cambias su programación, Mintlify recalcula el próximo tiempo de ejecución a partir de la hora actual. Las automatizaciones desactivadas no conservan un tiempo de ejecución pendiente.
 
+<div id="run-an-automation-manually">
+## Ejecutar una automatización manualmente
+</div>
+
+Puedes activar cualquier automatización habilitada bajo demanda sin esperar a su próxima ejecución programada o basada en eventos.
+
+1. Abre la página [Automatizaciones](https://app.mintlify.com/products/automations) en tu dashboard.
+2. Haz clic en el botón de ejecución <Icon icon="play" /> junto a la automatización que quieres iniciar.
+
+Las ejecuciones manuales usan la configuración actual de la automatización, cuentan para tu uso de créditos y aparecen en el historial de ejecuciones junto a las ejecuciones programadas.
+
 <div id="view-run-history">
 ## Ver el historial de ejecuciones
 </div>
@@ -146,3 +157,13 @@ Cada automatización mantiene un registro de las ejecuciones pasadas, incluido e
     <img src="/images/workflows/workflow-runs-light.png" alt="Página de ejecuciones de automatizaciones con los filtros de automatización y estado." className="block dark:hidden" />
     <img src="/images/workflows/workflow-runs-dark.png" alt="Página de ejecuciones de automatizaciones con los filtros de automatización y estado." className="hidden dark:block" />
     </Frame>
+
+Cada ejecución muestra uno de los siguientes estados:
+
+- **Queued**: La ejecución está esperando para comenzar. Las ejecuciones programadas se ponen en cola dentro de los 10 minutos siguientes a la hora programada.
+- **In progress**: El agente está trabajando activamente en la ejecución.
+- **Succeeded**: El agente finalizó la ejecución. Si la automatización realizó cambios, la ejecución enlaza con el commit o la pull request resultante.
+- **Failed**: El agente no pudo completar la ejecución. Las ejecuciones fallidas no cuentan para tu límite diario de ejecuciones.
+- **No changes**: El agente finalizó la ejecución pero no encontró nada que actualizar.
+
+Haz clic en una ejecución individual para ver su prompt, los archivos que leyó o modificó y cualquier pull request que haya abierto.
diff --git a/es/automations/reference.mdx b/es/automations/reference.mdx
@@ -6,6 +6,24 @@ keywords: ["predefinida", "automatización", "predeterminada"]
 
 Mintlify incluye automatizaciones predefinidas para las tareas de mantenimiento de documentación más comunes. Cada automatización tiene un prompt base y una configuración predeterminada. Puedes personalizar el activador, el modo de actualización y las instrucciones desde la página [Automatizaciones](https://app.mintlify.com/products/automations) en tu dashboard.
 
+<div id="at-a-glance">
+## De un vistazo
+</div>
+
+| Automatización | Activador predeterminado | Modo de actualización predeterminado | Repos de contexto | Configuración requerida |
+| -------------- | ------------------------ | ------------------------------------ | ----------------- | ----------------------- |
+| Update from code changes | Programación personalizada (dos veces por semana) | Pull request | Compatible | Al menos un repositorio de código fuente |
+| Draft changelog | Programación personalizada | Pull request | Compatible | Ninguna |
+| Draft improvements from assistant conversations | Programación personalizada | Pull request | No compatible | Ninguna |
+| Draft improvements from user feedback | Programación personalizada | Pull request | No compatible | Recopilación de comentarios activada |
+| Translate content | Actualización de contenido | Fusión directa | No compatible | Al menos un idioma de destino |
+| Fix broken links | Actualización de contenido | Pull request | No compatible | Ninguna |
+| Audit SEO metadata | Actualización de contenido | Pull request | No compatible | Ninguna |
+| Fix grammar & typos | Actualización de contenido | Pull request | No compatible | Ninguna |
+| Apply style guide | Actualización de contenido | Pull request | No compatible | Ninguna |
+
+Todos los valores predeterminados pueden cambiarse desde el panel de configuración de la automatización. Consulta [Configuraciones](/es/automations/manage#configurations) para ver las opciones disponibles.
+
 <div id="self-updating-content-automations">
 ## Automatizaciones de contenido autoactualizable
 </div>