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

# Sign-in and onboarding

> How signing in works, every step and field of the onboarding wizard, switching organizations and projects, and accepting an invite.

## Signing in

AgentHub signs you in with a one-time code sent to your email. There is no password to remember.

<Steps>
  <Step title="Enter your email">
    On the sign-in page, type your work email (the placeholder reads `you@company.com`). Select **Send me a code**, or press Enter.
  </Step>

  <Step title="Enter the code">
    AgentHub emails you a 6-digit code ("We emailed you a 6-digit code. Enter it above."). Type it in **6-digit code** and select **Verify & sign in**. Select **Use a different email** to go back.
  </Step>

  <Step title="Land in your work">
    If you were sent to the sign-in page from a specific link, you return there. Otherwise AgentHub opens the first project of one of your organizations on **Overview**; use the organization switcher to move to another. If you belong to no organization, you go to onboarding. If your organization has no project yet, you go to the onboarding step that creates one.
  </Step>
</Steps>

The first successful sign-in creates your account. You do not need to sign up separately.

### Single sign-on

As you type, AgentHub checks whether your email belongs to an organization that has Okta SSO configured, either as a member or through a pending invite. If it does:

* A **Sign in with SSO** button appears (or one **SSO: `<org name>`** button per organization, if there are several), next to **Email me a code**.
* If any of those organizations **enforces** SSO, the email-code button disappears and the page says "Your organization requires single sign-on."

See [SSO with Okta](/agenthub/settings/sso-okta).

### Sign-in messages

| Message | Meaning |
| - | - |
| Your access is pending approval by an administrator. | Your email is not approved for platform access. AgentHub records a request that a super admin can approve. See [Platform access](/agenthub/settings/platform-access). |
| Your organization (`<slug>`) requires single sign-on. Use "Continue with SSO" above. | An organization you belong to enforces SSO. Use the SSO button. |
| Enter a valid email. | The address is not a valid email. |
| Enter the 6-digit code we emailed you. | The code is not six digits. |
| Couldn't sign in with Okta. Contact your admin. | The Okta callback failed. |
| Couldn't start Okta sign-in. Check your SSO configuration. | AgentHub could not reach your Okta authorization server. |
| SSO is not configured for that organization. | The organization has no SSO configuration. |
| Organization not found. | The SSO link named an organization that does not exist. |
| SSO session expired. Try signing in again. | The SSO attempt took longer than 10 minutes or its cookies were lost. |
| Okta denied access. Ask your admin to assign you to the CorePillar app in Okta. | You are not assigned to the Okta application. |

### Password sign-up

A separate **Create your account** page at `/signup` takes a **Name**, **Email**, and **Password** (at least 8 characters). The sign-in page does not link to it, and password sign-in is turned off on the sign-in page, so email codes are the way in. Sign-up from an unapproved email returns "Thanks — your access request is pending approval by an administrator. We'll email you once you're approved."

## The onboarding wizard

Onboarding starts the first time you sign in without belonging to any organization, and again whenever an admin chooses **New organization** in the organization switcher.

The first screen, **How would you like to get started?**, offers two paths. "Picking one hides the other. You can run the other path later from the organization switcher."

| | Path A: Quickstart with pre-built templates | Path B: Custom system integration |
| - | - | - |
| Card button | **Start with a template** | **Connect my system** |
| For | Seeing AgentHub work on a realistic example | Connecting your own agent |
| Keys | Runs on the Platform Demo Key | Platform Demo Key or your own key |
| Steps | 2 | 5 |
| Ends in | Cost Calculator, with the template's agent loaded | Model Manager |

Inside a path, the progress rail at the top lets you jump back to any step you have already reached without losing what you typed. **Choose a different path** returns to the first screen and starts the other path clean. If you already belong to an organization, a **Back** button on the first screen returns you to the app.

### Path A: Quickstart with pre-built templates

<Steps>
  <Step title="Pick a template">
    Each card is a complete agent with a system prompt, tone, tools, and connectors. Selecting a card moves you to the next step. The available templates:

    | Template | Environment base |
    | - | - |
    | Conference Lead Deduplication | `cortex-leadops` |
    | Order to Cash Automation | `apex-o2c` |
    | Automated Hiring Process | `talon-hiring` |
    | HR Policy & Leave Management | `tally-leave` |
    | Contract Summarization | `sentrum-legal` |
    | Customer Support & Refund Resolution | `helios-support` |
    | IT Helpdesk & Access Provisioning | `atlas-itops` |
    | E-commerce Shopping Assistant | `vera-retail` |
    | Insurance Claims Triage | `sentinel-claims` |
    | Coding Agent Template | `forge-firmware` |
  </Step>

  <Step title="Name your workspace">
    | Field | Notes |
    | - | - |
    | **Organization name** | Only shown if you are not already inside an organization. "Your company or team. Members, keys, and billing live here." |
    | **Project name** | Pre-filled with the template name. |

    The page lists the five environments the template creates, built from its environment base, for example `helios-support_Test` through `helios-support_Development`. Select **Change** to pick another template, then **Create and open**.
  </Step>
</Steps>

AgentHub creates the organization (if needed) and the project, saves the template's agent as a draft, and opens the project's **Cost Calculator**. Runs there use the Platform Demo Key's \$50.00 allowance.

### Path B: Custom system integration

The path header reads "Five steps, in this order. Each one is saved as you go, and you can step back to any of them without losing what you have entered." A **So far** row of chips summarizes what you have chosen.

<Steps>
  <Step title="Connect system">
    **How will your system connect?** Pick one:

    | Option | What the card says |
    | - | - |
    | **EvalKit SDK** | Wrap your agent in one `init()` call. |
    | **MCP server** | Point your MCP host at CorePillar so tool invocations are traced. |
    | **REST ingest API** | POST JSON spans to `/api/v1/traces/ingest` with a tracing key. |

    **Which environment are you connecting first?** **Sandbox** (recommended first connection) or **Production**.

    <Note>
      This choice only changes the instructions shown at the end of onboarding. CorePillar has not published an SDK, so connect with the REST ingest API. See the [tracing quickstart](/agenthub/developers/tracing-quickstart).
    </Note>

    **Continue** stays disabled until you pick a connection method.
  </Step>

  <Step title="LLM keys">
    Choose how model calls are paid for:

    * **Use the Platform Demo Key**: \$50.00 of platform-funded usage on Anthropic models. "Best for evaluating CorePillar itself."
    * **Bring my own provider key**: "Required for production work." Then fill in:

    | Field | Notes |
    | - | - |
    | **Provider** | Anthropic, OpenAI, or Google. |
    | **API key** | A password field. The key stays in this browser tab until the organization exists, then is verified with the provider and encrypted into the vault. |
    | **Label (optional)** | For example "Production Anthropic key". |

    **Show me how to get a key** opens a walkthrough for the chosen provider, with an option to skip it and use the Platform Demo Key. **Actually, I want to add my own key** switches from the demo key to your own.
  </Step>

  <Step title="Create org">
    Enter **Organization name** and select **Create organization**. Your key from the previous step is saved now. If saving it fails, you see "The organization exists, but your API key was not saved" with **Go back and fix the key**. Coming back to this step later does not create a second organization.

    If you started onboarding inside an existing organization, this step is already complete.
  </Step>

  <Step title="Create project">
    Enter **Project name** (placeholder "Price Reconciliation") and select **Create project**. The hint shows which environment your first connection targets, such as `price-reconciliation_Test` for Sandbox or `price-reconciliation_Production` for Production.

    If you saved your own key, AgentHub adds that provider's default model to the project: GPT-4o Mini, Claude Haiku 4.5, or Gemini 3.5 Flash-Lite.
  </Step>

  <Step title="Upload instructions">
    Optional. Give AgentHub your agent's instructions so scenarios and evaluations are graded against them.

    * Drop a file on **Drop a Markdown file here**, or select **Choose a file**. Accepted: `.md`, `.markdown`, or `.txt`, up to 1 MB. The file is parsed in your browser with no model call.
    * Or paste into **Or paste the instructions**.

    A preview shows how many rules and tools were detected and the detected tone. "Nothing that looks like agent instructions was found" means AgentHub could not find a `# Title` plus a paragraph, or a `## System prompt` section.

    The **What happens when you finish** box summarizes the next steps. Select **Save and finish** (or **Finish without instructions**). The instructions are saved as a draft Cost Calculator run in the project.
  </Step>
</Steps>

You land in **Model Manager** to register your first model. Then [create a tracing key](/agenthub/settings/tracing-keys) and [send a trace](/agenthub/developers/tracing-quickstart).

### Onboarding errors

| Message | What to do |
| - | - |
| Give your organization a name. / Give the project a name. | Fill in the field. |
| An organization with a similar name already exists. Try a different name. | Organization slugs are unique across the platform. Choose another name. |
| Only admins can create organizations. | You already belong to an organization as an AI Builder or User. Ask an admin. |
| Only an admin can create projects. | Template projects need the Owner or Admin role. |

Errors appear in a "That did not work" box with **Try again**.

## Switching organization and project

The header shows two switchers separated by a slash: organization, then project.

* **Organization switcher:** lists every organization you belong to, with a check next to the current one. Choosing one opens its first project's Overview. Admins and super admins also see **New organization**, which starts onboarding for a fresh organization.
* **Project switcher:** lists the organization's projects and opens the chosen one on Overview. **New project** sits at the bottom.
* On Cost Calculator pages a third switcher picks the environment. Your choice is remembered per project in this browser.

## Creating more projects

Select **New project** in the project switcher. The **Create project** window says "A tracing key is created automatically for the new project."

| Field | Notes |
| - | - |
| **Project name** | Placeholder "My agent project". The slug is derived from it. |

Select **Create project**. AgentHub opens the new project's Overview.

Only Owners and Admins (and super admins) can create projects. Others see "You do not have permission to create projects." A duplicate name returns "A project with a similar name already exists."

<Note>
  The tracing key generated with a new project is never displayed, because its raw value is not shown anywhere. To send traces, create a new key under [Tracing keys](/agenthub/settings/tracing-keys).
</Note>

## Accepting an invite

When an admin invites someone without an account, AgentHub produces a link of the form `https://<site>/invite/<token>`. The admin shares it; AgentHub does not email it.

<Steps>
  <Step title="Open the link">
    If you are not signed in, you go to the sign-in page and come back to the invite afterwards. Your email must be approved for platform access first.
  </Step>

  <Step title="Sign in with the invited email">
    The invite only works for the exact address it was sent to.
  </Step>

  <Step title="Membership is created">
    AgentHub adds you to the organization with the invited role and opens it. If you are a User (Viewer), AgentHub shows the ModelHub-only screen; use [ModelHub](https://modelhub.corepillar.ai) instead.
  </Step>
</Steps>

If the invite cannot be accepted, a **Could not accept invite** page shows the reason and a **Go to dashboard** button:

| Reason | Fix |
| - | - |
| Invite not found or expired | Invites last 7 days. Ask for a new one. |
| This invite was sent to a different email address | Sign out and sign in with the invited email. |

If you were already a member, accepting the link just marks the invite used.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.