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.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.
The setup checklist
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.If multiple business units need isolation — separate data, separate users, separate billing — each is its own organization. See Organizations and projects for the full hierarchy.
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 for the full hierarchy and provider-specific setup.
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 for scoping guidance.
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.
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 for the role model.You don’t need teammates to start building. A single user can build, test, and run workflows end-to-end.
What you’ll have when you’re done
An organization
The top-level tenant for your users, projects, and data.
At least one LLM provider
Configured so agents can reason. Keys stored securely in the vault.
A project
Where you’ll build your first workflow.
Tools enabled
Whatever integrations your workflow will use.
Next: Build your first bot
Quickstart
Build a working web research bot in about 5 minutes
Five bots you can build today
Short recipes for the most common patterns — routers, researchers, analyzers, reviewers
Reference
Admin Portal
SuperAdmin controls for orgs, users, LLM providers, and security
Organizations and projects
The multi-tenancy hierarchy and scoping model
Model configuration
Full guide to configuring LLM providers at every level
Tools overview
Catalog of built-in integrations and custom tool options