> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/work-with-transformations-cp/run-your-transformation/inspect-your-data/publish-for-collaboration.md).

# Publish for collaboration

When you are ready to make your content available for others, you can publish it as a **data source**. The data source uses a **data service** that is automatically created on the step, and is available to other tools. You must be connected to your **repository** to publish the data source.

1. Click the **Publish data source** button ( ![Publish Data Source Button](/files/XZwgRzxGyylXDDE93ny8) ) at the top right of the header bar to open the Publish Data Source window.
2. Click **Get Started** to open the Publish Details window.

   Enter the data source information in the following fields:

   | Fields               | Description                                                                                                                                                             |
   | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | **Data Source Name** | The name used by other Pentaho applications when accessing your data source.                                                                                            |
   | **Server**           | The default value for this field is your current repository. You can select other repository connections, if you have created them, through the **Repository Manager**. |
   | **URL**              | The base URL string used to connect to the server.                                                                                                                      |
   | **User Name**        | The user name required to access the server. The user must also have publishing permissions.                                                                            |
   | **Password**         | The password associated with the provided user name.                                                                                                                    |
3. When you are done, click **Finish**.
4. Once your data source is created, a confirmation will appear. The data source should now be available on the server. Click **Close** to continue inspecting your data or click **View this in User Console** to open a new browser window and work with the data source in Analyzer.


---

# 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.pentaho.com/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/work-with-transformations-cp/run-your-transformation/inspect-your-data/publish-for-collaboration.md?ask=<question>&goal=<endgoal>
```

`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.