Skip to main content
Membership is managed from Settings → User Management. The older Members page now redirects there, so links to /<org-slug>/settings/members still work. This page explains the rules behind adding, inviting, changing, and removing members. For a field-by-field tour of the screen, see User Management.

​
Who is listed

User Management shows:
  • Every current member of the organization, under the box for their role.
  • Every pending invite, marked (pending invite).
Expired invites are not listed. Each member’s line also carries (owner) if they are an Owner and (you) for yourself.

​
Adding someone

Type their email into the box for the role you want and select Save changes. What happens depends on the address:
AgentHub does not send invite emails. Copy the invite link from the save summary and send it to the person yourself.

​
Roles you can assign

Owner cannot be assigned through an invite or User Management.

​
Invite details

  • Link format: /invite/<token>, where the token is 48 random hexadecimal characters. The link’s host is your deployment’s configured address.
  • Expiry: 7 days from when the invite was created or last re-sent.
  • One invite per email per organization. Inviting the same email again, or moving a pending invite to another box, replaces the old invite: it gets a new token, the new role, and a fresh 7-day expiry. The old link stops working.
  • Platform access first. An invite to an email that cannot sign in would be a dead link, so AgentHub refuses to create one until the email is approved. See Platform access.

​
Accepting

The invitee opens the link, signs in with the invited email, and becomes a member with the invited role. If the link has expired or they sign in with another address, they see Could not accept invite. Details are in Accepting an invite. If your organization uses Okta, an invitee can also sign in through SSO. A pending invite makes the Sign in with SSO button appear for their email, and the invite’s role is used unless an Okta group mapping assigns one. See SSO with Okta.

​
Changing a role

Move the email from one box to another and select Save changes. The summary shows “Role updated” with “Now <role>.”
  • You cannot change your own role (“You can’t change your own role.”).
  • Only a super admin can move someone into or out of Admins (“Only a super admin can add or change admins.”).
  • The organization’s last Owner cannot be demoted (“This is the org’s last Owner — can’t be demoted.”).
  • Moving a pending invite to another box re-issues the invite with the new role.

​
Removing someone

Delete the email from every box and select Save changes. AgentHub asks you to confirm: “Remove this person?” (or “Remove N people?”), “These emails are no longer in any box. Saving will remove their access to this organization (or revoke their pending invite).” Select Remove and save. You cannot remove yourself, only a super admin can remove admins or revoke admin invites, and the last Owner cannot be removed.
Removing someone from the organization does not stop them signing in to CorePillar. To block sign-in as well, a super admin should deny their email under Platform access. Do both when someone leaves.

​
Members across both products

Membership belongs to the organization, and ModelHub and AgentHub share it. Anyone you add can sign in to either site. Their role decides what they can do there: Users get ModelHub only, AI Builders and Admins get both. See Roles and permissions.