How does the platform layout adapt to the logged-in role?

The entire platform layout — menus, screens, dashboards, and even which dashboard widgets are visible — is governed by the logged-in user's role and permissions. When a user signs in, what they see is assembled from what their role is allowed to do: a vendor sees their workspace and their orders; a country manager sees their country's dashboard; fulfilment staff see the fulfilment queue; an…

The entire platform layout — menus, screens, dashboards, and even which dashboard widgets are visible — is governed by the logged-in user's role and permissions. When a user signs in, what they see is assembled from what their role is allowed to do: a vendor sees their workspace and their orders; a country manager sees their country's dashboard; fulfilment staff see the fulfilment queue; an admin sees the full back-office. This isn't just hiding buttons — controller actions are gated by the same module.action permissions, so the adaptation is enforced on the server, not just in the UI. The result is that each role gets a focused, relevant experience and can't reach functions outside their remit.