> ## Documentation Index
> Fetch the complete documentation index at: https://helpcenter.magure.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform setup

> Get your MagOneAI environment ready for building — organizations, projects, model providers, and tools

## Who this is for

You're setting up MagOneAI for the first time — for yourself, your team, or your organization. This walkthrough takes you from a fresh deployment to an environment where anyone can build a workflow.

If the platform is already set up and you just want to build, skip to the [Quickstart](/quickstart).

<Info>
  Most steps here require **Organization Owner** or **SuperAdmin** privileges. Builders don't need to repeat setup — once your org is configured, new projects inherit most of it.
</Info>

## The setup checklist

<Steps>
  <Step title="Access your organization">
    Sign in to MagOneAI. If your organization has already been created by a SuperAdmin, you'll land inside it. Otherwise, the SuperAdmin creates the organization from the [Admin Portal](/platform/admin-portal).

    If multiple business units need isolation — separate data, separate users, separate billing — each is its own organization. See [Organizations and projects](/platform/organizations-and-projects) for the full hierarchy.
  </Step>

  <Step title="Configure at least one LLM provider">
    Every agent in a workflow needs a language model to reason. You configure which models are available once, at the org (or platform) level, and builders select from those when creating agents.

    Decide which provider fits your needs — cloud (OpenAI, Anthropic, Google) for speed and capability, or private/self-hosted for data sovereignty. Configure API keys or endpoints in the Admin Portal. Credentials are stored in the secure vault and never exposed in workflows.

    See [Model configuration](/models/overview) for the full hierarchy and provider-specific setup.

    <Tip>
      Start with one provider. You can add more later — agents can be switched to a different model without rebuilding the workflow.
    </Tip>
  </Step>

  <Step title="Create a project">
    Projects live inside an organization and group related workflows, agents, tools, and knowledge bases. A typical setup uses one project per use-case area — "HR automations", "Sales workflows", "Customer support" — so teams work in isolation without stepping on each other.

    Create your first project from the Studio sidebar. Give it a descriptive name — it'll show up in every workflow you build inside it.

    See [Organizations and projects](/platform/organizations-and-projects) for scoping guidance.
  </Step>

  <Step title="Enable the tools your workflows will use">
    MagOneAI ships with first-party integrations — Google, Microsoft, databases, web search, and more. You enable the ones your team needs in the project's tool settings.

    Some tools need credentials up front:

    * **Web Search** — works out of the box, no credentials required. Good first tool to enable.
    * **File tools** — built in, no setup. Good for CSV/PDF processing.
    * **Google / Microsoft** — require OAuth setup the first time (platform admin configures the app credentials; end users connect their accounts).
    * **Databases** — require a connection string to your database.

    Start minimal — enable the tools you actually need for your first workflow. You can add more any time.

    Browse the [tools overview](/tools/overview) for the full catalog. For third-party MCP servers, see [External MCP servers](/tools/external-mcp-servers).
  </Step>

  <Step title="Invite your team (optional)">
    Other builders and end users can be invited to the organization with roles that match what they need to do — admins, builders, consumers. See [RBAC](/security/rbac) for the role model.

    You don't need teammates to start building. A single user can build, test, and run workflows end-to-end.
  </Step>
</Steps>

## What you'll have when you're done

<CardGroup cols={2}>
  <Card title="An organization" icon="building">
    The top-level tenant for your users, projects, and data.
  </Card>

  <Card title="At least one LLM provider" icon="brain">
    Configured so agents can reason. Keys stored securely in the vault.
  </Card>

  <Card title="A project" icon="folder">
    Where you'll build your first workflow.
  </Card>

  <Card title="Tools enabled" icon="wrench">
    Whatever integrations your workflow will use.
  </Card>
</CardGroup>

That's the whole base layer. From here, building workflows is a matter of dragging nodes on the canvas — no further configuration needed.

## Next: Build your first bot

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Build a working web research bot in about 5 minutes
  </Card>

  <Card title="Five bots you can build today" icon="bolt" href="/cookbooks/quick-bots">
    Short recipes for the most common patterns — routers, researchers, analyzers, reviewers
  </Card>
</CardGroup>

## Reference

<CardGroup cols={2}>
  <Card title="Admin Portal" icon="gear" href="/platform/admin-portal">
    SuperAdmin controls for orgs, users, LLM providers, and security
  </Card>

  <Card title="Organizations and projects" icon="sitemap" href="/platform/organizations-and-projects">
    The multi-tenancy hierarchy and scoping model
  </Card>

  <Card title="Model configuration" icon="brain" href="/models/overview">
    Full guide to configuring LLM providers at every level
  </Card>

  <Card title="Tools overview" icon="wrench" href="/tools/overview">
    Catalog of built-in integrations and custom tool options
  </Card>
</CardGroup>