> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/data-model/deployment-and-usage/view-based-deployment.md).
# View Based Deployment
Data models can be deployed to the server to provide accessibility to users. Depending on business needs such as controlled access of data, data consumption in ETL pipelines, analysis, etc. users may need to deploy data models separately. Astera Data Stack lets you deploy multiple subsets of a data model without creating separate data models and performing redundant tasks for each deployment using view-based deployments.
Views in a data model help you focus on a smaller group of the entities without considering the whole data model, thus enabling users to work incrementally. Deployment of these views lets us verify, deploy, and allow access to only those entities of the data model that are present in a view.
### How to Use View-based Deployment:
Consider an example of a dimensional model consisting of multiple fact tables. To work with fact tables individually, we can use views in the data model.
1. Create a View by clicking the *Add* *New* *View* icon located in the bottom left of the data model designer. A new view will be created.
2. Rename this View as per the requirements by either double-clicking it or by right-clicking the View tab and selecting the *Rename View option* from the context menu.
3. Now, add the desired entities to the view using any of the following methods:
* We can add entities to the View directly from the main model. To do this, right-click the entity that must be added to the view, use the Add to View option in the context menu of entities and select the view.
* We can also add entities to the View by selecting any entity from the data model browser and dragging-and-dropping it onto the designer. Press the shift key while dragging-and-dropping to ensure that the selected entity and all the entities that are connected to it are added to the View on the designer.
Having added the desired entities onto the designer, the Views can now be used for incremental designing.
After finalizing the Views, they can be deployed to the server.
4. To deploy a view, Use the *Deploy Data Model* icon from the toolbar or the short cut key, *Shift+Alt+M*.
5. A wizard will open. Here, name the deployment and select the Views that need to be deployed. Once done, click *OK*. If the data model is verified successfully, the Views will be deployed and available on the server.
{% hint style="info" %}
**Note:** When deploying Views, each view will be verified for read and write deployment individually without taking into account other Views. Separate deployments for each View will also be created.
{% endhint %}
---
# 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://documentation.astera.com/data-model/deployment-and-usage/view-based-deployment.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.