ATS

Work alongside selected ATS intake paths.

Omniteam can work alongside selected ATS intake paths without replacing the system that manages your pipeline. The provider, permissions, webhooks and usable data direction are confirmed during setup.

Add an evaluation layer beside the ATS

The ATS continues to manage the pipeline while selected hiring context supports review in Omniteam.

ATS

Job and candidate context

The provider remains the pipeline system of record.

Connection

Scoped intake

Permissions, webhooks and supported fields shape what can move.

Omniteam

Role-specific evaluation

Criteria, interviews and review material remain connected.

Adapter source exists. Account setup, scopes, webhooks, marketplace approval and live sync vary. Configuration required for each provider.

Calendar

Coordinate events and meeting capture from your calendar.

Connect a configured Google Calendar or Microsoft Outlook calendar. Calendar access can provide scheduling context for the interview workflow. Provider and account configuration are required.

Connect scheduling context to the right interview

Calendar access supports coordination without becoming a universal Microsoft 365 or Google Workspace claim.

Calendar

Google Calendar or Microsoft Outlook

Use a configured calendar provider.

Interview event

Role and candidate context

Keep the scheduled event connected to the relevant workflow.

Capture path

Provider-specific setup

Confirm availability and consent before relying on capture.

Not a Microsoft 365 or Copilot app claim. Provider and account configuration required.

Meeting capture

Capture supported external meetings where configured.

Capture paths exist for Teams, Zoom, Google Meet and Webex through calendar and meeting-provider configuration. Each path has different maturity, consent and failure states. Not automatic recording everywhere. Not a Teams-distributed Omniteam app.

Show the full meeting-capture journey

Meeting support depends on the provider, tenant, bot and consent configuration.

1
Meeting provider
Teams, Zoom, Google Meet or Webex
A configured provider supplies the meeting path.
2
Capture gate
Consent and account configuration
Capture is not automatic on every platform.
3
Processing
Transcript and speaker attribution
Quality and failure states remain reviewable.
4
Omniteam review
Source-linked evidence
People inspect the result before using it in a debrief.

Provider, tenant, calendar and bot configuration dependent. Not automatic recording on every platform. Not a Teams-distributed Omniteam app.

Connected AI Apps

Use selected Omniteam recruiting workflows from a connected AI workspace.

Use selected Omniteam recruiting workflows from a connected ChatGPT or Claude workspace in private or custom organizational setups. Not public marketplace availability. Other custom MCP clients supported under controlled protocol and setup conditions. Writes require preview plus separate in-app human approval.

Keep connected AI actions bounded and reviewable

Connected assistants can find or prepare supported information. Writes require a separate in-app approval path.

Find and review

Search accessible Omniteam records

Return a bounded result and open the exact record in Omniteam.

Allowlisted deep link

Act with control

Preview, validate and confirm

The user reviews the requested action before a supported write is completed.

Explicit approval required

Private or custom organizational connection only. No public marketplace availability or universal MCP-client compatibility. Chat wording is never approval. Preview is mutation-free and confirmation rechecks the exact action and user.

Add structured interview evidence without replacing your ATS.

Connection boundaries

ATS and candidate/job data

What stays, what connects, what Omniteam adds.

Keep each connection boundary explicit