Restrict Elementor Widgets
Per-role access control for the Elementor editor, published on WordPress.org. An administrator decides which widgets, columns and sections each role may use, and the editor stops offering the rest.
What the work involved
Restrict Elementor Widgets is per-role access control for the Elementor editor. An administrator picks which widgets, columns and sections each role is allowed, and everyone else opens a canvas that simply does not offer the rest.
The problem it solves is an agency problem. A site handed to a client comes with a page builder that can undo the design it was built to protect: a client editing their own copy is welcome, a client dropping an unstyled widget into a carefully built template is a support ticket. Narrowing the palette is what makes handing over the keys safe.
Doing that correctly means the restriction has to hold in the editor rather than only in the interface. A widget hidden from a panel but still reachable is not access control, so the rules are enforced where Elementor asks what a user may insert, not where the list is drawn.
It is published on WordPress.org, which sets the same bar every listed plugin meets: escaped output, sanitised input, a prefixed namespace, and no traffic to anywhere the site owner did not ask for. Roles and capabilities come from WordPress itself rather than a parallel permissions system, because a plugin that invents its own idea of who an editor is will disagree with the site around it.