> For the complete documentation index, see [llms.txt](https://help.marcopayroll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.marcopayroll.com/marco-user-guide-x4/2025/marco-platform-structure/vendor-portal/vendor-data-cloud.md). # Vendor Data Cloud Vendor Data Cloud is a centralized place to allow Vendors to store and manage data objects such as employee data types, pay items, leave types and public holidays for all of their Customer. The data cloud helps streamline and create a SSOT of all the data objects that will be used across different customers. To set up your data cloud, you can either import data objects from Marco’s Global Library or set it up manually. Marco’s Global Library contains all the data objects in different categories such as employee information, pay items, leave types and public holidays. Each item within the dictionary is ensured to follow statutory requirements or commonly used information within organizations. Begin setting up your data cloud by importing data object from countries that you currently have Customers or Staff that your customers has. Once data objects has been imported, you can also create your own data objects based on your needs or customer requirements. Any data objects created in the Vendor Data Cloud will be set as defaults across all Customer Portal. --- # 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://help.marcopayroll.com/marco-user-guide-x4/2025/marco-platform-structure/vendor-portal/vendor-data-cloud.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.