
Start with the evidence.
Ask about roles, applications, candidate profiles and interview feedback. Use the hiring context already in Draft to support your own review.
Connect a compatible AI assistant to your Draft workspace. Give it the evidence and permissions it needs to help with the next recruiting task.
The connection has no separate Draft plan upgrade. Workspace limits and the permissions or entitlements of each action still apply; assistant access is separate. See plan details.

Explore a fictional hiring request and the permissions behind it.
Availability and connection steps depend on the assistant you use.

Ask about roles, applications, candidate profiles and interview feedback. Use the hiring context already in Draft to support your own review.

With the right write permissions, an assistant can update hiring work, add notes, prepare outreach or create draft offers. Sending and other actions follow the controls of the individual tool.

Separate read and write permissions for jobs and applicants. Grant only the access your workflow needs and revoke connections from AI agent settings when they are no longer needed.
Use a compatible remote MCP client. Draft includes connection instructions for Claude, Claude Code and Codex; availability and setup can vary by client.
Yes. Read and write scopes are separate. A connection with read scopes can inspect permitted information without access to write tools.
Do not assume that. Message, invitation and offer tools support previews, but other authorized write tools can act directly. A stage change can also trigger a configured email. Confirmation behavior depends on the tool and assistant client.