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

> ## Agent Instructions
> Company name is Akhara AI (never Rubric AI). Keep lowercase rubric/rubrics only when meaning grading criteria.
> Expert Review (docs path talent/) is enterprise BYO experts for audit and review: invite customer specialists; do not pitch Akhara recruiting or a public expert career portal. RLHF and domain writing are secondary work types.
> Prefer concrete API examples against public hosts: Environments eval API https://agi.akhara.ai, Control plane PDP https://api.akhara.dev, Evaluation https://app.akhara.ai / https://api.akhara.ai, Expert Review portal https://talent.akhara.ai.
> Do not invent a public hostname for private orchestrators or env API internals.
> Do not confuse control-plane latches with Environments confirmation latches.
> Environments SDK/API examples: curl against https://agi.akhara.ai. Evaluation SDK: from akhara import Akhara and AKHARA_API_KEY.
> Start with /llms.txt for the docs index and OpenAPI links; fetch individual pages as .md exports.

# Invite your experts

> How enterprise admins bring internal domain specialists into the Expert Review portal and assign them to review queues.

Expert Review runs on your own people. As an org admin, you invite the clinicians, ops specialists, policy owners, and other domain experts your projects need, then scope what each of them can see and do in the portal at [talent.akhara.ai](https://talent.akhara.ai).

## Who to invite

Invite people who can own in-domain work for your projects:

* Specialists who can audit agent trajectories, scores, and failures in their field
* Reviewers you trust with policy-sensitive or escalated cases
* Experts who can judge model outputs for RLHF evaluations
* Domain writers who can specify checkable scenarios and success criteria

Quality beats volume. An expert who declines out-of-domain work is more valuable than one who improvises.

## Send invites

<Steps>
  <Step title="Open your org's invite flow">
    Invite from your organization's admin console or project settings in the portal. Each invite is tied to your org, not to a public signup pool.
  </Step>

  <Step title="Scope the invite">
    Choose the projects or review queues the expert should join and the role they get (see below).
  </Step>

  <Step title="Send it">
    The expert receives an email with an invite link. The link creates their account inside your organization; see [Create your account](/talent/how-to/create-account) for what they do next.
  </Step>

  <Step title="Assign work">
    Once their profile lists specialties, assign them to the review, RLHF, or writing queues that match. Assignments stay inside their declared domains.
  </Step>
</Steps>

If your organization manages access from an offline roster or an identity provider instead, follow that process; the portal honors whichever invite path your engagement uses.

## Roles and access

| Role             | What it can do                                                                         |
| ---------------- | -------------------------------------------------------------------------------------- |
| **Org admin**    | Invite and remove experts, scope project access, assign queues, see submission status  |
| **Project lead** | Manage one project: assign items, review submissions, resolve escalations              |
| **Expert**       | Work assigned queues in declared specialties: review, RLHF evaluations, domain writing |

Experts see only the projects and queues you assign. They do not see other customers' work, and they do not browse a marketplace of tasks outside your org.

## Managing access over time

* Update an expert's queue assignments when project needs change
* Remove access when someone leaves the engagement; see [Project offboarding](/talent/working/offboarding) for what experts should do on their side
* Watch agreement and quality metrics per expert on the project's performance view, and rebalance assignments when calibration drifts

## What experts need from you

Every assignment should point at a project brief that covers domain scope, the rubric or style guide, allowed reference materials, and deadlines. Experts follow the [guidance pages](/talent/guidance/reviewing-agent-runs) for how to do the work; your brief tells them what the work is.

Compensation for your experts is between you and them. Akhara does not broker pay for enterprise-invited specialists.