Skip to content

Admin Tools (Simple Overview) ​

Admin tools help you manage providers, policies, users, and system data. This page explains what each tool is for in plain language.

What admins can do ​

  • Test APIs from the browser
  • Export data for reports
  • Navigate quickly between related pages
  • Duplicate settings to save time

View as role (preview) ​

Next to your profile icon in the top bar, admins see a View as control (eye icon). Use it to preview the app exactly as a different role sees it — handy for demos, testing, and day-to-day decluttering.

  • Open the View as dropdown and pick a role (Account Owner, Accountant, Manager, Developer, Security Custodian, Member, or User).
  • The left sidebar instantly hides the admin sections that role can't see. A blue banner — "Previewing the app as …" — stays at the top so you never forget you're in a filtered view.
  • Your choice is remembered in this browser, so the decluttered view survives page reloads.
  • Click Exit view (in the banner) or pick (your role) from the dropdown to return to your full admin view.

Important: this is a display-only preview. It changes what you see, not what you can do — the server still grants you your real permissions, and it never affects other users. The control only appears for admins and account owners.

API Console ​

Use the API Console to try endpoints without leaving the dashboard.

  • Pick an endpoint
  • Edit the example request
  • Send the request and view the response
  • Export the response if needed

This is useful for troubleshooting and learning how the API behaves.

  • Breadcrumbs show where you are and let you jump back.
  • Related links suggest the next page you might need.

These save time when you manage providers, routing, or policies.

Export data ​

Export buttons let you download data as JSON or CSV for reports and audits.

Package-managed provider groups ​

Super admins can define provider/model bundles at package level.
When a company is assigned a package, provider groups are synced automatically:

  • Package Managed groups are generated from package bundle definitions.
  • BYOK Auto group is generated from the company's own active BYOK models not covered by package bundles.
  • Custom groups are company-managed and editable only with the right permissions.

Why this matters ​

  • One bundle change can apply to all companies on that package.
  • Replacing a model in a package bundle no longer requires per-company manual updates.
  • Company admins use the synced portfolio, plus their own BYOK models where allowed.

Ownership model ​

  • Super admin manages package bundles and sync.
  • Company admin/project owner uses available groups and can manage only custom groups (if granted routing.providerGroups.manage).

Tips ​

  • Use the API Console to validate changes before production.
  • Export reports regularly if you track compliance or costs.