> 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/use-case-studies/welcome-to-the-platform.md). # Welcome to the Platform Joe Black sipped his coffee, staring at the login screen of his company’s **white-label instance of Marco OS**. As the **Vendor Admin** for his organization, **Global Workforce Solutions (GWS)**, he had full control over how the system was set up. It wasn’t just a tool; it was the backbone of how they managed global payroll, compliance, and contractor operations for their clients. GWS specialized in helping businesses expand internationally by managing their remote workforce. By leveraging their **white-label instance of Marco OS**, they provided their clients with a seamless platform under their own branding, giving them the power of Marco OS while maintaining their unique identity. Today was a big day—GWS had just signed a new client, **Stellar Tech Solutions**, and it was up to Joe to onboard them smoothly. He glanced at his inbox and found an email from a colleague: {% hint style="info" %} **Subject:** New Company Setup & Admin Manager Request Hey Joe, Hope you’re doing well! We’ve got a new customer coming onboard, and I need your help setting them up in the system. Can you create a new company profile on the platform and assign an internal staff member as the Admin Manager for that company? #### **Company Details** * **Company Name:** Stellar Tech Solutions * **Company Code:** STS2025 * **Industry:** IT Services * **Location:** Singapore #### **Admin Manager Details** * **Name:** Sarah Wong * **Email:** * **Role:** Admin Manager * **Profile Type:** Manager * **Responsibilities:** Overseeing company operations on the platform, managing staff accounts, and handling compliance tasks. * **Additional Permissions:** Access to payroll reports and contractor onboarding. Let me know once it’s done or if you need anything else from my end. And of course, if the UI steps are a bit foggy, just say the word—I’ve got your back. Thanks, Joe! Best,\ M {% endhint %} Joe cracked his knuckles and got to work. * For **Stellar Tech Solutions'** setup, he referred to the [**Adding a Customer**](/marco-user-guide-x4/2025/marco-platform-structure/vendor-portal/vendor-portal-features/home.md) guide. * For **Sarah Wong’s onboarding**, he followed the [**Staff Onboarding**](/marco-user-guide-x4/2025/marco-platform-structure/customer-portal/manager-guide/people-management/employee-transition/staff-onboarding.md) guide. * To ensure she was correctly set up as a **Manager**, he checked the [**Profile Type**](/marco-user-guide-x4/2025/introducing-marco-os/user-roles-and-profiles/profile-types.md) guide. * To confirm she had the appropriate access, he consulted the [**Managing System Access**](/marco-user-guide-x4/2025/marco-platform-structure/customer-portal/manager-guide/people-management/employee-transition/managing-system-access.md) guide. Following the documented steps, he: * **Created a new company profile** – Added Stellar Tech Solutions and entered the relevant details. * **Assigned the Admin Manager** – Navigated to the “Users” tab and selected “Add Staff.” * **Entered Sarah Wong’s details** – Set her role as **Admin Manager** and profile type as **Manager**. * **Configured additional permissions** – Granted access to payroll reports and contractor onboarding. * **Sent the activation email** – Sarah received her credentials and onboarding instructions. After double-checking his work, Joe hit **"Save."** The new company and its Admin Manager were now live on the platform. One more successful setup in the books. He took a sip of coffee and leaned back—just another day in the life of a **Vendor Admin at GWS**. *** **Next Episode:** TBD --- # 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/use-case-studies/welcome-to-the-platform.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.