Skip to main content
This guide is for organization admins and super admins. It takes you from an empty organization to employees chatting on modelhub.corepillar.ai, without giving them the rest of the platform.

​
The short version

  1. Connect models in AgentHub’s Model Manager, on the project employees will use. Include a cheap, a mid-range and a frontier model.
  2. Approve their emails in Settings → Platform access (super admins), one address or a whole @domain.
  3. Add them as Users in Settings → User Management, and share the invite links.
  4. Send them https://modelhub.corepillar.ai, not the AgentHub address.
1

Connect models in AgentHub first

Employees have no Model Manager in ModelHub and cannot fix a missing model themselves. Without one they see “No models available yet” and cannot send anything.
  1. Sign in to AgentHub.
  2. Open Model Manager in the project employees will use, add a provider API key, and attach models. See Model Manager.
Which project? When an employee signs in with an email code, ModelHub sends them to the first project (by creation order) in their organization that has a model attached. When they accept an invite link, they land on the organization’s first project, whether or not it has models. The simplest setup is to connect models to the organization’s first project.Chat spends on your organization’s own provider keys. If a model’s key is revoked or rejected, ModelHub tries your organization’s other keys for the same provider before failing the message.
2

Choose a spread of models

Auto routing sends each message to the cheapest connected model that can handle it. With one model connected, everything goes to that model and there is nothing to save.Connect at least one model from each size:Sizes are derived from price and model family, as explained in How routing works. Ordinary questions go to Small by default, so in a typical workplace most traffic lands on the cheapest model.Avoid reasoning-only models as your only option: they can spend their whole output budget thinking and return no answer.
3

Approve their emails

Nobody can sign in with an email code until their address is approved. This happens before, and separately from, organization membership.In Settings → Platform access (visible to super admins only), add either:An explicit decision about one address beats the domain rule both ways. Employees who try to sign in before approval are recorded as pending requests you can approve. See Platform access.If your admins are not super admins, ask your organization’s super admins to do this step.
4

Add them as Users

In Settings → User Management, type each email on its own line in the Users box (“ModelHub only.”) and click Save changes. See User Management.The Save summary shows one line per email:
CorePillar does not email invites. Share each invite link yourself. Links expire after 7 days. The token works on either hub, so you can send the ModelHub form of the link: https://modelhub.corepillar.ai/invite/ followed by the token.
The older Members settings page now redirects to User Management. Roles are explained in Roles and permissions and Members.
5

Hand out the right URL

If a User opens an AgentHub link, they see “Your account has ModelHub access only” with a Go to ModelHub button.
6

Check it works

Ask one employee, or a test account approved and added as a User, to:
  1. Sign in at ModelHub with an email code.
  2. Confirm the sidebar shows only New chat, Chat, AI Usage and their history, with no Settings.
  3. Send a message and see an answer with a report card.
  4. Open AI Usage and see My AI usage.

​
Using Okta SSO instead of email codes

If your organization signs in with Okta, configure it in SSO (Okta). On first sign-in, each employee’s membership is created automatically with a role from their Okta groups or your default SSO role. Set the default role to Viewer so employees arrive as Users. If you enforce SSO, the email-code option disappears for your members. The SSO button on the sign-in page only appears for emails that are already members of, or have a pending invite to, your organization.

​
Things to know before you start

  • Approve and invite together. An approved email with no invite can still sign in. With no organization to join, that person is sent to onboarding, where they can create an organization of their own. Invite people as you approve them.
  • The role matters on AgentHub, not ModelHub. On ModelHub an Admin and a User see the same chat. What differs is whether they can open AgentHub and see settings and organization-wide usage. See Access control.
  • Organization-wide usage. Owners, Admins and super admins see an Organization | Just me toggle on the AI Usage page, on both hubs, including the itemised log of removed personal data. Users only ever see their own numbers.
  • Encrypted history (optional). Super admins can turn on end-to-end encryption of chat history from Settings → General. Employees then need to set a passphrase to reopen their own chats. Tell them before you turn it on.
  • Some features use CorePillar’s platform key. Conversation titles, the routing second opinion and the AI layer of privacy screening run on a small model billed to CorePillar, not to your keys. If that key is unavailable, those steps are skipped: titles fall back to the first line of the message, routing uses the score alone, and screening uses its pattern layers only.

​
Removing someone

See Access control. In short: remove them in User Management, and remove their address from the Platform access allowlist if it is listed there.