Industry Insights
What Is Ogloba’s Role and Permission Function?
What does Ogloba’s permission module do? It lets administrators define Back Office user roles, control function-level actions, and manage access across countries, business units, and areas precisely.
Granular Control for Back Office Users
System administrators can create, define, search, and edit user roles within the Ogloba Back Office. Each role can be configured around specific functions and access levels.
Permissions are not limited to broad menu visibility. Administrators can control access down to individual actions within a function. This includes buttons such as submit, approve, and reject. As a result, different users can participate in the same operational process while retaining clearly separated responsibilities.
Multilevel Organizational Management
Ogloba supports a multilevel permission structure across countries, business units, and areas. This allows clients to configure user access according to their real organizational model.
A country manager, business unit user, area operator, and central administrator can each receive access aligned with their responsibilities. This makes the platform adaptable to complex retail operations and distributed management structures.
Conclusion
Ogloba’s permission modules help organizations manage Back Office access with precision. The platform supports clear roles, controlled actions, and multilevel operational governance.
FAQ
Can we restrict a Back Office user to specific actions like approve or reject, rather than an entire menu?
Yes. Ogloba’s permissions go beyond menu visibility down to individual actions within a function, including submit, approve, and reject buttons. This lets several users work in the same operational process while keeping their responsibilities separated.
How does Ogloba’s permission structure map to a multi-country retail organization?
The platform supports a multilevel permission structure across countries, business units, and areas. A country manager, a business unit user, an area operator, and a central administrator can each be given access that matches their actual responsibilities.
Who manages roles in the Ogloba Back Office, and what can they do?
System administrators create, define, search, and edit user roles directly in the Back Office. Each role is configured around specific functions and access levels, so access rights stay aligned with the organizational model as it evolves.
Do we have to set permissions for every individual user, or are they assigned through roles?
Ogloba’s Role and Permission function is a role-based access control capability, so access is configured on the role rather than set up separately for each person. Each role is defined around specific functions and access levels, and a user receives the access of the role that matches their responsibilities. That is what keeps administration scalable as the number of Back Office users grows.
