Devise Invitable权限控制：权限不足时跳转至角色对应仪表盘

Hey there! Since you already have role-based redirection working for your login flow, we can leverage that same pattern to update the invite page's behavior. Here's how to adjust things step by step:

1. Locate Your Permission Check Logic #

First, find where you're restricting access to the invite page. This is probably in your InvitesController (or whichever controller handles the invite page) as a before_action method, or part of a permission callback.

For example, your existing code might look like this:

# app/controllers/invites_controller.rb
before_action :authorize_invite_access

private

def authorize_invite_access
  # Only admins and dispatchers can access the invite page
  unless current_user.administrator? || current_user.dispatcher?
    # Current behavior: redirect to root_path
    redirect_to root_path, alert: "You don't have permission to access this page."
  end
end

2. Replace Root Path with Role-Specific Dashboard #

Since you already have logic to redirect users to their role-based dashboards after login, you can reuse that exact logic here. If you have a helper method (like user_specific_dashboard_path) that maps roles to their respective dashboards, just swap root_path with that method.

Example Updated Code: #

def authorize_invite_access
  unless current_user.administrator? || current_user.dispatcher?
    # Redirect to the user's role-specific dashboard instead of root
    redirect_to user_specific_dashboard_path(current_user), alert: "You don't have permission to access this page."
  end
end

3. If You Don't Have a Reusable Helper (Yet) #

If your login flow handles redirection inline instead of using a helper, create a reusable method to keep your code DRY. Add this to your ApplicationHelper (or a dedicated helper file):

# app/helpers/application_helper.rb
def user_specific_dashboard_path(user)
  case user.role
  when 'manager'
    manager_dashboard_path
  when 'employee'
    employee_dashboard_path
  when 'client'
    client_portal_path
  # Add all your other roles here
  else
    root_path # Fallback for unknown roles
  end
end

4. Test the Behavior #

Make sure to test with different role accounts:

• Log in as an admin/dispatcher: Verify you can still access the invite page.
• Log in as a manager/employee/client: Verify you're redirected to your specific dashboard instead of the root path.

This approach keeps your code consistent with existing patterns, which makes maintenance easier down the line—even once you pick an authorization library later!

内容的提问来源于stack exchange，提问作者Shawn Wilson