FAQ: Authorization - Admin Role II

This community-built FAQ covers the “Admin Role II” exercise from the lesson “Authorization”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Ruby on Rails: Authentication

FAQs on the exercise Admin Role II

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head here.

Looking for motivation to keep learning? Join our wider discussions.

Learn more about how to use this guide.

Found a bug? Report it!

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

When an admin wants to delete a recipe, he/she doesn’t have an access to recipe (application redirect him/her to the list of cuisines.

So, I think that instead of

class RecipesController < ApplicationController

  before_action :require_user, only: [:show, :edit, :update, :destroy]
  before_action :require_editor, only: [:show, :edit]
  before_action :require_admin, only: [:destroy]

in Recipes Controller should be this (update method instead of show method):

before_action :require_editor, only: [:edit, :update].