Controlled application email, never mass ATS submission
Approve one immutable recipient, body, and resume package for 24 hours.
The stored posting must explicitly accept email applications and contain the recipient.
“Accepted by provider — delivery unverified,” never submitted or delivered.
Loading workflow access…
Separate permission
Email connection
Your RoleSharp login never grants sending access. Connect a mailbox separately with send-only permission. RoleSharp cannot read, search, or modify your inbox.
Loading connections…
Disconnect is local-first: credentials are erased and pending sends are canceled before any best-effort provider revocation. Microsoft does not expose an equivalent per-token revocation endpoint, so local erasure remains authoritative.
Email applications only
Application Queue
Review the exact recipient, subject, body, resume attachment identity, fit, and evidence confidence. Jobs requiring an ATS form stay manual.
Loading application queue…
Safety boundaries that always apply
- • Separate Gmail or Microsoft permission; login identity is never reused for sending.
- • Source-backed recipient and explicit email-application instruction required.
- • One attempt per canonical job and a 14-day canonical-company cooldown.
- • User daily limit 1–5, capped again by the administrator limit.
- • Pause, disconnect, and deletion win before the durable provider-call boundary.
- • Unknown provider outcomes are terminal for automatic retry and show no resend control.
- • Official links remain visible for ATS-only and otherwise blocked jobs.
- • Access tokens, refresh tokens, resumes, and message bodies never enter queue payloads.
Eligibility is posting-backed; outcomes remain deliberately conservative.
A queue item can advance only when the stored posting explicitly accepts email applications, supplies the recipient, and passes consent, cap, cooldown, duplicate, and immutable-package checks.
Read the methodology- Fit and evidence confidence are not hiring probabilities
- Provider acceptance is recorded as delivery unverified
- Unknown outcomes cannot trigger an automatic retry
- ATS-only and ambiguous-recipient jobs remain manual
What Auto Apply does — and does not do
Can it apply everywhere?
No. It supports only explicit application-by-email instructions in the stored posting. ATS forms, job-board flows, screening questions, and ambiguous recipients stay manual.
Can RoleSharp read my mailbox?
No. Gmail requests gmail.send plus basic identity. Microsoft requests delegated Mail.Send and User.Read only to confirm the connected account. No inbox-read or modify scopes are requested.
What does evidence confidence mean?
It measures how much reliable profile and posting evidence supports the fit calculation. It is not a hiring, interview, or delivery probability.
Review the job and resume package before authorizing email.
Daily Matches keeps the source posting and fit evidence visible. Campaign settings then define the consent mode, thresholds, daily cap, and expiry.