When userscripts can be executed manually or automatically, bookmarklets are only available for manual execution. Users need to click a bookmark stored in their browser to execute the code. Besides this limitations bookmarklets have the same advantages for users in the sense that they are free to choose their tools, but need to find, install, and update their bookmarklets individually.

Userscripts for Confluence makes it easy to quickly install userscripts and make them available for a selected audience. This way the usability of scripts can be tested in a production environment under defined conditions. For instance in specified locations (spaces or pages) or for a group of users or individual users.

In this scenario users are no longer free to use the install any scripts they need. So Therefore if the administration team does administrators do not install a particular userscript, it is not available.

Experienced users may be best served by classic userscripts or bookmarklets. This way they are in full control over which code to execute under which circumstances.

For unexperienced less experienced users it is probably easier to allow the administration team to provide the additional services by central installation. The burden of selecting the tools, checking the code for security and other issues, and updating the code for new versions or due to alteration of the Confluence server is then located on the administration team. The administration team may choose between a simple app like Userscripts for Confluence or choose to create one or more projects to provide these additional features by their own app. The time to get code in production, to add users, or remove a function is typically significantly shorter with Userscripts for Confluence than creating a new app.