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.

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

1. 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.

2. Scope the invite

   Choose the projects or review queues the expert should join and the role they get (see below).

3. Send it

   The expert receives an email with an invite link. The link creates their account inside your organization; see Create your account for what they do next.

4. Assign work

   Once their profile lists specialties, assign them to the review, RLHF, or writing queues that match. Assignments stay inside their declared domains.

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 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 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.