> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/setup-and-admin/business-hubs/connecting-your-paid-social-apps/meta-for-work.md). # Meta for Work - [Configure SSO and user provisioning between Meta and Okta via Meta Work Accounts](https://help.cerby.com/setup-and-admin/business-hubs/connecting-your-paid-social-apps/meta-for-work/configure-sso-and-user-provisioning-between-meta-and-okta-via-meta-work-accounts.md): This article describes how to configure single sign-on (SSO) authentication and automatic user provisioning with Okta via Meta Work Accounts - [Explore the Meta for Work tools for user and asset management](https://help.cerby.com/setup-and-admin/business-hubs/connecting-your-paid-social-apps/meta-for-work/explore-the-meta-for-work-tools-for-user-and-asset-management.md): This article describes the Meta for Work tools available to manage user access and your business assets and how they relate to Cerby. - [Meta for Work tools for admins](https://help.cerby.com/setup-and-admin/business-hubs/connecting-your-paid-social-apps/meta-for-work/meta-for-work-tools-for-admins.md): This article describes the tools and the basic management actions that admins can perform in the Meta Business Manager. - [Meta for Work tools for end users](https://help.cerby.com/setup-and-admin/business-hubs/connecting-your-paid-social-apps/meta-for-work/meta-for-work-tools-for-end-users.md): This article describes how to use Meta Work Accounts as an end user to access your organization’s Meta for Work tools. --- # 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://help.cerby.com/setup-and-admin/business-hubs/connecting-your-paid-social-apps/meta-for-work.md?ask=&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.