Default Landing Pages for Various User Types

Hi ​@asubramaniam, Great questions, this comes up often for customers with multiple user types, so let me walk through how landing behavior works in Eightfold and what's configurable.

1. Does Eightfold have a default Home Page per User Type?

Yes, but it's driven by a user's default role/access mode rather than by custom-defined user types. In general:

• Employee role users land in Career Hub (the internal talent/job hub experience)
• Talent Acquisition users land on the TA landing pages (e.g., Positions Home / Requisitions)
• Hiring Managers are a distinct role with TA-side access on requisitions they own or follow, but their landing page still follows their default role

So the system routes users based on their primary role — not on a per-user-type homepage mapping like "TA Staff → Page X, Talent Design Staff → Page Y."

2. Why are landing pages inconsistent when impersonating?

This is expected behavior when users hold multiple roles. The system keys off the user's default role/access mode at login. For example, a user with both Employee and Hiring Manager roles will land in Career Hub if Employee is their default role — even though they have TA-side responsibilities. During impersonation, you're seeing each user's effective default role play out, which can feel inconsistent if role assignments vary across your test users.

3. Is there a configuration screen to set Landing Pages per User Type?

There isn't currently a single Admin Console screen that maps user type → landing page. However, there are a few supported levers:

• Default role assignment (most reliable): Since landing is driven by default role, ensure each user's default role matches the experience they should start in. Role assignment is managed through Admin Console, file ingestion, SSO/JIT provisioning (which supports a configurable default role), connectors, or User APIs.
• Redirect configuration: A URL redirect can route users hitting the home/index URL to a specific destination (e.g., redirecting / to a careers or positions page).
• Career Hub landing URL config: For Career Hub deployments, a landing_page_url value (e.g., /positions_home) can influence where users land. Note this is URL routing rather than persona-aware homepages.

Best practices

1. Audit default roles first. For dual-persona users (e.g., Employee + Hiring Manager), be deliberate: if they primarily work in TA, don't leave Employee as their default role.
2. Standardize role assignments in your Sandbox test users so impersonation behaves predictably — inconsistent landing pages in Sandbox usually trace back to inconsistent default role setups.
3. Use redirect/landing URL configs where you need deterministic routing beyond what roles provide.
4. Document the experience-switching path for hybrid users so they know how to move between Career Hub and TA.

Documentation

• User Management in Eightfold — roles, provisioning methods, and role assignment mechanisms
• Resource Management Personas — platform persona definitions (Employee, Recruiter, Hiring Manager, Admin)