Shell, users & roles

Configure MongoDB Shell

Palryn uses the real mongosh executable for Shell tabs. Install it separately, then set Settings → Tools → mongosh executable if it is not on PATH. Enter an executable name or full path without command-line arguments.

Open Shell from the application menu or Explorer's Shell button. Right-click a database and choose Open Shell to preselect that database. The launcher lets you choose a saved connection and initial database.

Run a script

Enter commands and choose Run script, or press Ctrl/Command + Enter in the editor:

db.getName()
show collections
db.orders.find({ status: "pending" }).limit(10)

Each run starts a fresh mongosh process and executes the whole script. Variables and database changes last for that run only; the next run starts in the tab's selected database. Opening or restoring a Shell tab never runs its script automatically.

Output appears when execution ends. Document results can appear as read-only grids between text sections; use Text for the plain transcript. A normal process exit can still include individual command errors, so read the output.

Stop shell cancels the local process, but does not roll back commands already sent to MongoDB. Shell runs have a five-minute execution limit and output limits. Running a script retires existing query cursors on that connection; rerun query tabs before editing their documents.

Choose a replica-set member

Automatic routing follows the saved URI's routing and read preference. Refresh servers discovers advertised data-bearing replica-set members and their current roles. Selecting a member pins the Shell connection to it.

Member roles are a discovery snapshot. Advertised hosts must be reachable, and selecting a secondary does not make it writable. The Database field accepts a manually entered name even if metadata listing is unavailable.

Manage users

Right-click a database and choose Manage users and roles…. The Explorer background menu also offers this action, initially targeting admin. Use Change database to select an authentication database.

1. Open the Users tab.
2. Create a user or edit an existing one.
3. Set the supported authentication details and direct role assignments.
4. Review the edited fields and save explicitly.

Users are listed in their authentication database, not every database they can access. Existing usernames cannot be renamed. Password-only changes do not replace unchanged roles or custom data. User administration requires the corresponding MongoDB privileges.

Manage roles and privileges

Open the Roles tab to view built-in roles and manage custom roles. Each inherited role has a source database identifying where that role is defined.

In the Visual privilege editor, add a resource scope, then choose its allowed actions. Available scopes include a collection, a database's normal collections and cluster-level operations. Suggestions are grouped and searchable; MongoDB remains the authority on supported privileges and resource combinations.

Advanced BSON retains direct privilege definitions that need source editing. Unsupported visual shapes remain in source instead of being silently simplified. Review direct grants separately from inherited/effective details. Save changes explicitly; deleting a role also removes its grants from users and roles that inherit it.