Why did I see the workspace checkpoint instead of a login form?
Valerian sends users through the configured identity provider from /login. /entry is the checkpoint after sign-in.
FAQ
Workspace access and product questions.
Answers for the public landing page, access checkpoint, role-scoped workspaces, Research Assist, and trust posture.
Access
Login, entry, and workspace access
How Valerian handles access before a user reaches an org-scoped workspace.
Does the access page create a new sign-in session?
Yes. /login starts the configured provider sign-in flow and Valerian creates its own secure app session only after the provider callback is validated.
Is /login the same as /entry?
/login starts sign-in. /entry requires a valid Valerian app session before workspace access is checked.
Why did /entry send me back to /login?
That means the checkpoint did not find a valid Valerian app session for this environment.
What should I do if the checkpoint says no active session was found?
Return to /login and complete provider sign-in. If sign-in succeeds but workspace access is still pending, ask an org admin to confirm your account and role.
Who can approve workspace access?
Workspace access is organization-managed. Your org admin, RevOps owner, or assigned Valerian owner should confirm whether your account and role are approved.
What does pending approval mean?
Your account may be recognized, but an organization admin still needs to approve or assign the workspace role before privileged pages are available.
What happens after an active session is found?
Valerian keeps the secure app session active while organization membership and role routing are checked.
Can I bookmark /entry?
Yes, but it is a checkpoint rather than the sign-in start. If your app session is not active, it sends you back to /login.
What if I belong to more than one organization?
Valerian routes active sessions into the organization and role resolved for that account. If the destination looks wrong, ask an org admin to verify the assigned role and organization.
Workflow
How the product is organized
What users see once they are inside the role-scoped product.
Who is Valerian for?
Valerian is for CRO commercial teams that need sponsor intelligence, account context, and action follow-through to stay connected.
What problem does the platform solve?
Sponsor movement, research context, handoffs, and action queues often live apart. Valerian keeps the signal, reason, and next move in one role-aware workflow.
What does an ADR or BD user see?
ADR and BD users focus on next actions, account context, outreach support, and evidence attached to the work they can move now.
What does a manager see?
Managers see team pressure, blocked work, stale pipeline motion, priority cues, and research-backed actions that may need intervention.
What do admins and RevOps users control?
Admins and RevOps users manage settings, integrations, access posture, governance, and rollout readiness where their role allows it.
What is an action?
An action is a role-scoped piece of work with context, priority, status, and a reason it matters.
What if there is no assigned work yet?
Empty workspace states should explain whether work is unavailable, not assigned yet, gated by access, or waiting for upstream context.
Does Valerian replace operator judgment?
No. The product keeps context and recommended moves visible so teams can make better decisions without hiding the human review step.
Research Assist
Research Assist and action context
How research appears in the product without becoming a detached assistant.
Is Research Assist a chat interface?
No. Research Assist is structured support embedded inside opportunity, trial, manager, and action workflows.
Where does Research Assist appear?
It appears where research can clarify a concrete action, opportunity, trial, sponsor, or manager workflow state.
Is there a separate research dashboard?
No. Research stays attached to the action and workflow surfaces where it is useful.
What does Research Assist show?
It can show freshness, confidence, provenance, source and signal counts, recommended move, evidence references, and why an action matters.
What does "Why this action" mean?
"Why this action" explains the research or workflow signal behind the recommended move so an operator can review the reason before acting.
What is a recommended move?
A recommended move is the next operational step suggested by the available context. It is meant to guide review, not bypass judgment.
What are evidence references?
Evidence references point to the structured signals or source cues that support the action context.
Can Research Assist generate context everywhere?
No. It appears only where the workflow supports structured research context, action attribution, and reviewable output.
What if Research Assist is unavailable?
Unavailable means the research context could not be loaded or generated at that moment. It is different from low confidence or no access.
States
Freshness, confidence, and access states
What the main labels mean across manager, action, admin, and research surfaces.
What does fresh mean?
Fresh means the research or workflow context is recent enough to support normal review.
What does needs refresh mean?
Needs refresh means the context is aging or stale enough that operators should refresh before relying on it for a major decision.
What does low confidence mean?
Low confidence means the context needs review before a major move. It is a quality cue, not a command to stop all work.
What does blocked mean?
Blocked means a dependency, permission, context gap, or workflow state must clear before the work can move.
What does unavailable mean?
Unavailable means a surface or upstream context could not be loaded at that moment. It should be treated differently from no access or low confidence.
What does read-only mean?
Read-only means your role can review the surface, but changes are restricted.
What does admin-gated mean?
Admin-gated means only organization admins can change that setting, connector, or governance control.
What does unauthorized mean?
Unauthorized means the requested surface is not available to the current account or role.
What does no access mean?
No access means Valerian could not resolve a workspace role that allows the requested surface.
Trust
Trust, controls, and operating posture
How Valerian keeps access, integrations, and rollout posture explicit.
How is privileged backend access handled?
Privileged backend calls are made from the server-side dashboard runtime. Browser code does not receive privileged backend credentials.
Does Valerian expose privileged credentials in the browser during login?
No. Access checks stay behind the server-side dashboard runtime, and privileged credentials are not sent to browser code.
Does the platform require broad backend CORS?
No. Privileged browser-direct backend calls are not part of the current posture.
How are workspaces scoped?
Authenticated users enter org-scoped routes, and role surfaces are resolved from that organization context.
Why are some integrations read-only first?
Read-only-first integration posture lets teams validate visibility, access, and operational fit before enabling broader write paths.
Who manages admin settings?
Organization admins manage settings, connectors, governance, and role-sensitive controls where their access allows it.
How should teams validate a rollout?
Start with public route checks, then auth checkpoint behavior, then role-by-role workspace QA with manager, ADR, admin, read-only, and pending access sessions.
What should I report if something feels wrong?
Capture the route, the state label you saw, the role you expected, and whether the issue happened before or after the workspace checkpoint.