Admin Settings UI

Admin Settings is the web console for administering Posit Package Manager. Sign in with a global:admin session and Settings appears in the user menu in the top-right corner of the navigation bar.

Signing in

Important

Create the first global:admin token with the CLI. After signing in with that token, you can create additional tokens from the web UI. See Creating API Tokens.

  1. Sign in to Package Manager with an admin token.
  2. Open the user menu in the top-right corner of the navigation bar and select Settings.
  3. Pick a feature from the sidebar.

User menu open for an administrator, showing the Theme switch, Settings, and Sign Out

No Settings item in the user menu? Your session is not global:admin. Sign back in with an admin token, or ask whoever holds the admin token to issue you one.

Available features

Feature What it does Docs
Overview Instance metadata, license summary, and a filterable feature grid grouped by category. Overview page
Experimental Features Turn opt-in preview features on and off. Experimental Features
Token Management Create, view, filter, and revoke API tokens. Token Management
Package requests Review, approve, and deny the packages that users request. Package requests

Permissions

Most pages under Settings require a global:admin session. A package_requests:admin session can only use the Package requests page.

To create an admin token, use Creating API Tokens from the CLI, or use Token Management from the UI once you already have that first token.

Troubleshooting

Settings not in the user menu

Your session is not global:admin. Either the token you signed in with lacks that scope, or you signed in as a repository-scoped user. Sign back in with an admin token.

Permission denied

A permission error can mean the token lacks the required scope or is no longer valid. Sign in again with a global:admin token.

Data does not load

The page renders but the cards stay blank. Usually the browser cannot reach the Package Manager server, or the token has gone stale:

  1. Open the browser console and look for failed API requests.
  2. Confirm network connectivity to the Package Manager server.
  3. Reload the page (Ctrl+R or Cmd+R).
  4. Sign out and back in.
Back to top