Designing Role-Based Access and Localization in an Enterprise React App

One of the biggest learning experiences for me at Kosheewas working with enterprise authorization models and GraphQL-based data access patterns. Prior to this role, most of my experience involved traditional REST APIs and relational databases. Working within a production GraphQL environment required me to think differently about how data is queried, mutated, cached, and managed throughout the application.

I contributed to administrative workflows allowing organizations to manage users, groups, locations, cameras, and role assignments. These workflows relied heavily on role-based access control (RBAC), where permissions and access rules span multiple organizational levels and determine what data users can view, modify, or manage within the platform.

One of the biggest shifts for me was learning how to work with GraphQL and Apollo Client. Much of my previous experience involved REST APIs and relational databases, so I had to learn how queries, mutations, caching behavior, and authorization rules interacted within a production GraphQL application.

I also gained significantly more experience working with Redux Toolkit. Although I had previously used Redux in my bootcamp projects, working within a production application required a deeper understanding of state management patterns, shared user state, slices, asynchronous actions, and application-wide data flow.

• Frontend: React, Redux Toolkit, TypeScript, i18next
• API: GraphQL, Apollo Client, RBAC
• Testing: Bruno, Jest, React Testing Library
• Outcome: Enterprise administration workflows supporting users, groups, roles, locations, and localization

This project taught me that building enterprise software is often less about writing components and more about understanding how data, permissions, state management, and business rules interact across an entire system.