> For the complete documentation index, see [llms.txt](https://docs.zenml.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenml.io/pro/core-concepts.md).

# Core Concepts

- [Hierarchy](https://docs.zenml.io/pro/core-concepts/hierarchy.md): Understanding ZenML's hierarchical structure
- [Organizations](https://docs.zenml.io/pro/core-concepts/organization.md): Manage organizations in ZenML
- [Workspaces](https://docs.zenml.io/pro/core-concepts/workspaces.md): Learn how to use workspaces in ZenML Pro.
- [Projects](https://docs.zenml.io/pro/core-concepts/projects.md): Managing projects in ZenML
- [Teams](https://docs.zenml.io/pro/core-concepts/teams.md): Learn about Teams in ZenML Pro and how they can be used to manage groups of users across your organization and workspaces.
- [Snapshots](https://docs.zenml.io/pro/core-concepts/snapshots.md): Trigger pipelines from the dashboard, SDK, CLI, or REST API.
- [Triggers](https://docs.zenml.io/pro/core-concepts/triggers.md): Trigger pipelines by schedule or event.
- [Webhooks](https://docs.zenml.io/pro/core-concepts/webhooks.md): Receive authenticated events from external systems in ZenML.
- [Slack](https://docs.zenml.io/pro/core-concepts/webhooks/slack.md): Connect the Slack Events API to a ZenML webhook endpoint.
- [GitHub](https://docs.zenml.io/pro/core-concepts/webhooks/github.md): Configure and test GitHub webhook delivery to ZenML.
- [ClickUp](https://docs.zenml.io/pro/core-concepts/webhooks/clickup.md): Configure and test ClickUp webhook delivery to ZenML.
- [Custom webhooks](https://docs.zenml.io/pro/core-concepts/webhooks/custom.md): Send signed custom events to a ZenML webhook.
- [Resource Pools](https://docs.zenml.io/pro/core-concepts/resource-pools.md): Fair GPU and compute sharing for AI/ML teams: dependable production capacity, shared pools, idle reuse, and organization-level resource governance.
- [Core Concepts](https://docs.zenml.io/pro/core-concepts/resource-pools/resource-pools-core-concepts.md): Definitions for ZenML Pro resource descriptors, pools, classes, policies, requests, selectors, and leases.
- [Admin Guide](https://docs.zenml.io/pro/core-concepts/resource-pools/resource-pools-admin-guide.md): How platform admins configure resource descriptors, pools, classes, target bindings, policies, and grants in ZenML Pro.
- [User Guide](https://docs.zenml.io/pro/core-concepts/resource-pools/resource-pools-user-guide.md): How pipeline authors request pooled resources with ResourceSettings and inspect Resource Manager requests.
- [External Workloads](https://docs.zenml.io/pro/core-concepts/resource-pools/resource-pools-external-workloads.md): How external workloads use ZenML Pro resource pools through service accounts, direct Resource Manager requests, and priority-lane policies.
- [Reconciliation Process](https://docs.zenml.io/pro/core-concepts/resource-pools/resource-pools-reconciliation.md): How resource pool reconciliation, queueing, accounting, preemption, and lease management work at runtime.
- [Examples](https://docs.zenml.io/pro/core-concepts/resource-pools/resource-pools-examples.md): End-to-end resource pool use cases for CPU queues, GPU node pools, cloud machine types, licenses, external workloads, governance schedulers, and policy patterns.


---

# 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://docs.zenml.io/pro/core-concepts.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.