# How do I send each role to its own page after login?

> Add a Login Redirect Rule per role on the Login component. Use the User Menu's Logout Redirect Rules for logout, and page rules to route users by status.

Source: https://tadabase.com/docs/faq/how-do-i-redirect-each-role-after-login  
Status: Verified Nov 22, 2026. Checked against the current product

Open your Login component's **Login Redirect Rules** tab and add one rule per role (**If Role is** a role, **Then redirect to** a page); anyone no rule matches goes to the app's home page. For where people land after logging out, use the User Menu's **Logout Redirect Rules**, and use page rules to send users with a certain status, such as accounts waiting for approval, to one page.

## After login

- Click **Add New Redirect Rule** for each role. A rule for **All Users** matches everyone.
- A user who matches several rules (for example a user with two roles) goes to the page of the **last** matching rule, so put the most specific rules at the bottom.
- **Override redirect rules if user was redirected from a protected page** sends users back to the page they were trying to open instead.
- To keep some roles or statuses from logging in at all, use **Allowed Roles** and **Allowed Status** on the component's **Options** tab, each with its own error message.

## After logout

Edit the User Menu component, open **Logout Redirect Rules**, click **Add New Redirect Rule** and pick a page for each role. See [Add a user menu with login and logout links](https://tadabase.com/docs/pages/user-menu).

## Users waiting for approval or rejected

- New sign-ups get no role from the Signup component. If your pages are limited to roles, a user without one is kept out, and **Redirect to another page** under the page's **Select an action for non-authorized users** can send them to a "waiting for approval" page.
- To route by the **Status** field instead, add a page rule on the pages they might open: condition on the logged-in user's status, action **Redirect to an existing page**. Page security is checked before page rules, and when several rules match, the one lowest in the list decides.
- To stop them logging in at all, set **Allowed Status** to **Specific User Status** on the Login component and write the **Custom Error Message For Status**.

Details: [Login component](https://tadabase.com/docs/pages/login#redirect-rules), [Page rules](https://tadabase.com/docs/pages/page-rules) and [Page security](https://tadabase.com/docs/pages/page-security).
