<?php

use App\Providers\RouteServiceProvider;

return [
    'guard' => 'web',
    'middleware' => ['web'],
    'auth_middleware' => 'auth',
    'passwords' => 'users',
    'username' => 'email',
    'email' => 'email',
    'views' => true,
    'home' => '/dashboard',
    'prefix' => '',
    'domain' => null,
    'limiters' => [
        'login' => 'login',
        'two-factor' => 'two-factor',
        'registration' => 'registration',
    ],
    'redirects' => [
        'login' => '/dashboard',
        'logout' => '/login',
        'password-confirmation' => null,
        'register' => '/onboarding/step-1',
        // After the user clicks the verify-email link, send them to
        // onboarding step 1 instead of /dashboard. In anti-spam mode the
        // user was held at /email/verify before reaching onboarding, so
        // they have no workspace yet — landing on /dashboard would just
        // bounce them via the no-workspace check anyway. /onboarding/step-1
        // is the right "first real screen" after verification, and the
        // step-1 controller itself routes already-onboarded users to
        // /dashboard, so the redirect is correct for repeat verifies too.
        'email-verification' => '/onboarding/step-1',
        'password-reset' => '/login',
    ],
    'features' => [
        \Laravel\Fortify\Features::registration(),
        \Laravel\Fortify\Features::resetPasswords(),
        \Laravel\Fortify\Features::emailVerification(),
        \Laravel\Fortify\Features::updateProfileInformation(),
        \Laravel\Fortify\Features::updatePasswords(),
        \Laravel\Fortify\Features::twoFactorAuthentication([
            'confirm' => true,
            'confirmPassword' => true,
        ]),
    ],
];
