Loading workspace settings...
Sign in to manage hiring settings
Use your Bytebeam or AIEQU Mobility Google account to continue.
Continue with GoogleSettings
Manage communication, candidate sources, AI usage, and real-user performance.
Codex token usage
Daily usage across the hiring platform, in India Standard Time.
No Codex calls recorded in this period. Usage will appear after the first recorded AI request.
Daily usage
Usage by use case
¹ Cached tokens are included in input. ² Reasoning tokens are included in output. Total = input + output; these subsets are not added again. Older records may omit the cached or reasoning breakdown.
View daily numbers
Hiring mailboxes
Candidate email is routed through the mailbox for the reviewer's organization. Both mailboxes synchronize mail and calendars.
Applications by email
Forward an email with attached resumes to [email protected]. AI uses the resume, email, and current job descriptions to select a role, then adds the application to Linear and the review pipeline.
PDF and Word resumes are supported, including attachments inside forwarded .eml emails. Up to 25 MB per resume. New mail is checked automatically; screening follows in the normal pipeline.
Loading email intake status...
Only imports needing attention are listed here. Imported applications and their emails are available on candidate pages.
Naukri recruiter
Import mapped job applications into Linear, including contact details and the original resume.
Sign-in and OTP verification run automatically through the shared hiring mailbox.
Job mappings
Only mapped jobs are imported. Exact title matches are selected automatically.
| Naukri job | Applications | ATS role | Import status |
|---|
Connect and run the first sync to discover Naukri jobs.
Email templates
Your manager template applies to emails you send, including candidates in other managers' roles. A role override takes priority. If you have no saved template, the role's hiring manager default is used, followed by the system default. Independent outreach uses your own template. Additional CCs can be customized; candidate recipients, required reviewer copies, attachments, and workflow updates remain controlled by the application.
Performance
From the user's action to the updated screen, across the hiring platform.
No user actions recorded for this selection. Browse the app, then refresh here. New timings arrive within about 10 seconds.
Daily response time (milliseconds, IST)
Green: p50 (typical). Blue: p95 (slow). Days without successful actions show zero; incomplete actions are excluded from percentiles.
Actions
Slow interactions: open for recorded stages
Recent errors
Server endpoints, including background requests
All server requests in the selected period. Action and page filters apply to browser interactions.
How these timings work
Actions include clicks, shortcuts, form submissions, filters, and typing. Timings end after tracked work and the resulting paint. Sending email ends when the page has responded and advanced; background delivery is separate. Resume timings include loading and decoding the visible pages.
Server time comes from the application. Network + proxy is an estimate: browser time to the first response byte minus application time. It includes proxies and transport; it is not a pure network round-trip measurement. Missing measurements are shown as Unknown.
Trace stages overlap: a request contains server work, and server stages may contain other stages. Do not add all rows together. Browser/other excludes the union of foreground reads and media, and includes local work, scheduling, and painting. TLS is part of connect time. Background refreshes and prefetches do not extend an action.
Recorded across signed-in users. Timings contain route shapes and opaque session/request IDs, without field contents, email text, resume content, or names. Traces are bounded and retained for up to 30 days; hidden, cancelled, or timed-out interactions remain visible but do not count as successful latency samples.