Operator workspace
This login link came from a hiring operator workspace. The bridge can safely keep Tool as the first suggested stop without leaving the hiring site first.
This operator request stays on the local bridge first so the Tool-first lane stays visible before you leave for HospiEdge Tool. This keeps the operator path explicit without pretending the hiring app already owns shared sessions. Your return path inside the hiring app stays local to Pipeline.
Tool was requested, and Tool remains the safest first stop for this email.
Because this request came from an operator workspace, the supporting copy keeps HospiEdge Tool first unless active Schedule access is already confirmed on the same email lane.
This login link came from a hiring operator workspace. The bridge can safely keep Tool as the first suggested stop without leaving the hiring site first.
Return to the hiring pipeline after you finish here.
Operator pages already imply the HospiEdge Tool lane, so this bridge keeps Tool as the visible first stop while staying local until you choose to leave.
Use the same email in Schedule after Tool, or after this read-only check confirms active Schedule access.
This operator entry keeps the Tool-first expectation visible while it checks the same shared email lane locally. Use it before you leave the hiring app.
Enter the email you expect to use in HospiEdge Tool first. The hiring site will only run a read-only check when the shared integration database is available.
This is a read-only operator bridge check only. It does not create sessions, share passwords, or mint SSO tokens from the hiring app.
The bridge keeps operator traffic on one local decision page first, then lets you leave for the right app in a visible order.
Operator surfaces keep a Tool-first expectation visible, but they still do not mint sessions, share passwords, or claim full SSO.
This page helps you choose the next sign-in path. It does not create shared sessions or single sign-on from the hiring site.