User List
A ready-to-integrate list for users, built on Document List.
Ready-made user listing
User List extends Document List with user-oriented defaults. The consuming application maps its user collection and can adapt the visible fields, row actions and links without rebuilding search or pagination.
In APPNETOS DNS Control, AppnetosDnsControl\Admin\User\UserList maps AdminUserCollection.
The overview displays username, active state and a delete action. A user is shown as active only
when
the document is active and not locked.
How lists work
Unlike a picker, a Document List renders its initial rows immediately during the normal page response. Search and pagination refresh the relevant list content asynchronously with AJAX, avoiding a full page reload. The underlying document collection is queried for the requested page rather than rendering the entire collection.
Lists can display clickable links, boolean indicators and JavaScript-driven buttons. The application controls which data is exposed in each row and which actions are available. Authorization must still be enforced by the application and its server-side endpoints.
DNS Control implementation
protected function getCollection(): BaseUserCollection|null
{
return Registry::get(AdminUserCollection::class);
}
The application overrides getFields() and getRows(array $documents) to
build
links to the user editor, status indicators and JavaScript delete actions. The application prevents
deleting the currently authenticated administrator and the last remaining DNS Control super
administrator; these are application-specific safety rules, not generic list behavior.
Customizing User List
- Override
getCollection()to provide the intended user collection. - Override
getFields()to control the table columns. - Override
getRows()to configure username links, status and actions. - Use inherited AJAX search, pagination, sorting and template extension points.
Templates, Bootstrap and translations
The shared list renders through versioned Bootstrap templates. Supported Bootstrap versions are maintained in the Core App, while all templates can be replaced by application-specific Twig files. Core Apps that need translations provide them in 81 languages. Custom column labels and application actions can use the host application’s own translations.