How user and role data are loaded
Users list: Fetched from FleekDash endpoint (e.g. GET /wp-json/fleekdash/v1/users) with optional role and per_page. Response is formatted for the grid (avatars, display names, roles). Cache may be used (e.g. with cache bypass on first load or manual refresh).
Roles list: Fetched for the role filter and for the Role Management drawer (e.g. via fetchRolesOptimized or platform API). Includes native and custom roles with capability data.
Update user: User profile updates (name, email, avatar, etc.) and role updates use FleekDash or WordPress REST endpoints (e.g. PUT /fleekdash/v1/users/:id, PUT /fleekdash/v1/users/:id/roles). Authentication uses the same FleekDash auth (e.g. nonce).
Role create/update/delete: Role Management uses WordPress's role and capability system. Create, update, and delete roles via the FleekDash or WordPress API so existing plugins and core continue to work.
<!-- seo-geo: content-enrichment -->
In practice
User & Role Management — users list, roles, update user, role create/update/delete. On this page, How user and role data are loaded is covered in detail: what it looks like in the admin, the exact controls it exposes, and how it behaves when you use it day to day. Because how user and role data are loaded is part of User & Role Manager — a redesigned users grid, role management, application passwords, and inline role changes — the settings you touch here interact with the rest of the feature; when in doubt, open the feature overview and follow the docs in order.
See also
Need a hand? Contact support or head back to the User & Role Manager guide.