> For the complete documentation index, see [llms.txt](https://docs.bird.com/connectivity-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/connectivity-platform/third-party-risk-management/how-are-vendors-managed.md). # How are vendors managed? Within MessageBird a clear distinction is made between two categories of third parties; vendors and suppliers. **A supplier** is a third party providing communication connectivity services to MessageBird. **A vendor** is a third party providing ‘ancillary services’, required for the day-to-day business operations. These services do not directly affect the communication products as part of the CPaaS environment. In order to ensure that third party security management is applied consistently and continuously throughout the provision of the services, third party vetting procedures have been defined and implemented: * Third-Party Vendor Vetting Procedure * Third-Party Supplier Vetting Procedure MessageBird manages third party services and security by applying a strict risk based approach. --- # 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.bird.com/connectivity-platform/third-party-risk-management/how-are-vendors-managed.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.