It’s common to have a senior team member or an architect oversee the product and perform all the code reviews. This is a bad idea. The obvious reason is that having only one person perform code reviews will be a bottleneck to productivity for the team. The more subtle issues involve learning and shared responsibility.
When you give someone a code review you share a little responsibility for their code. You are looking at it and understanding it. You are also teaching each other how to be better programmers. No single team member has a monopoly on wisdom. Sharing code review responsibilities is a way to share knowledge and help everyone become a better engineer.