Skip to main content

​
Overview

The Team item at the bottom of the sidebar opens the Admin Panel — the admin-only home for everything organization-wide. It covers five areas:
  1. Team: the roster of every member, with roles and activity
  2. Merge factories: combine factories from across the organization into one
  3. Organization Memories: shared knowledge Dexter applies in every factory
  4. Integrations: connect your organization’s systems and write the notes Dexter reads when it uses them
  5. Usage & billing: your organization’s credit usage and charges by month (shown only to organizations on usage-based billing)
Members don’t see the Team item. They can open personal Settings from their account menu. If a member needs a role changed, they should reach out to an admin on their team.

​
Team Roster

The Team section lists every user in the organization. Columns:
  • Email: the user’s work email (your own row is marked “you”)
  • Role: Member or Admin, changeable from the dropdown on each row (see Changing a Role)
  • Joined: when the user’s account was created
  • Last active: how recently they used the platform
  • Actions: per-user actions, including Impersonate for member accounts
The roster sorts by email, join date, or last-active time — click a column header.

​
Roles at a Glance

These roles govern team administration. Product features still need to be enabled for the account; an Admin role does not unlock every optional feature.
There’s no limit on how many admins an organization can have, and at least one admin must exist at all times: ProDex won’t let you demote or remove the last admin. Keep at least two so team management never depends on a single person.

​
Changing a Role

Click the role dropdown on a user’s row to promote them to Admin or demote them to Member, then confirm the change. Role changes apply from the user’s next page load. In some organizations, the Admin role is managed by ProDex rather than by the organization’s own admins. In that case the Team section reads “Admin roles in this tenant are managed by Prodex.”, roles appear as plain text instead of a dropdown, and admins can’t be removed from this page. To add or remove an admin, ask your ProDex representative.

​
Impersonating a Member

Admins can click Impersonate on a member’s row to open ProDex as that user — useful for troubleshooting a teammate’s setup or seeing exactly what they see. Impersonation is available for Member accounts only; admins cannot impersonate other admins.

​
Removing a Member

Click the trash icon on a member’s row and confirm to remove them; you can’t remove yourself or the last admin. Removing a user deactivates their account rather than deleting their data: their factories, conversations, memories, and uploaded files are retained server-side. If the user is re-added later, their access and previous work are restored — they don’t start fresh.

​
Merge Factories

The Merge factories tool combines two or more factories — from any owners in the organization — into a single new factory:
  1. Enter a name for the new factory (and an optional description)
  2. Select 2–20 factories from the list; filter by owner if the list is long
  3. Click Merge selected
Shared entities, lookup tables, and constants are kept once in the merged result; anything that overlaps by name is preserved under both originals so nothing is silently dropped.
The merge list shows every factory in the organization with its owner. Admins can see factory names and owners across the whole tenant here, even though day-to-day work in a factory remains scoped to its owner — see Factory Management.

​
Organization Memories

Organization memories are shared knowledge files and assets that admins curate for the entire team: glossaries, process conventions, organization-wide defaults, logos, or any operational context that should be consistent across the organization. Dexter can use them in every factory in your organization, while each factory’s rules continue to govern that user’s preferences. Create and edit text entries from the Admin Panel with New File, or add a PNG or SVG with Upload Asset. Members can’t browse or edit organization memories from their factories — they simply benefit from Dexter applying them. For how they interact with factory-scoped knowledge, see Organization Memories.
Instead of each team member teaching Dexter the same conventions factory by factory, capture them once as organization memories — terminology, naming standards, and operational rules stay consistent everywhere.

​
Integrations

Integrations connect Dexter to your organization’s systems, such as your ERP, MES or data warehouse. They are organization-wide: once connected, Dexter can use them in every factory in your organization. Dexter only reads from an integration; it can’t change anything in the connected system. This section shows your organization’s integrations under Connected and the systems you can connect yourself under Available:
  • Connect a system listed under Available. The dialog walks through the setup steps in that system, then asks for the connection details. ProDex checks them with the system before saving anything.
  • Manage a connected integration to see when it was last checked and how many queries it ran today, run Test connection, Disable or Enable it, use Replace credentials when its secret expires, or Disconnect it.
  • On an integration’s Docs tab, click Add doc for a documentation file (.md, .json, .txt, or .csv), such as query patterns or a glossary of field names, or edit or delete an existing one. Dexter can read these files but not change them.
Integrations marked Managed by ProDex were set up by the ProDex team, which keeps their connection details and credentials; you can still edit their docs. To connect a system that isn’t listed, ask your ProDex representative. If nothing is connected or available, the section reads “No integrations yet.”
Good integration documentation is the fastest way to improve Dexter’s answers from a connected system: describe what each table or endpoint holds, which fields matter, and any codes or abbreviations your team uses.

​
Usage and Billing

The Usage & billing section shows your organization’s credit usage and charges for one Billing month at a time. It appears only for organizations on usage-based billing; if your organization has no billing contract with ProDex, the section is hidden.
  • Billing month: pick which month to view. Only months covered by your billing contract are listed.
  • Plan summary: your pooled credit allocation, licensed seats, and the price per credit beyond the allocation. Usage past the allocation is billed as overage — nothing is blocked.
  • Pooled credit usage: a bar showing credits used against the allocation, with any overage and its cost.
  • Per-user table: each member’s Conversations and Total Usage (credits) for the month, followed by the licensed-seat charge, any overage charge, and the Total cost.
  • Export CSV: downloads the month’s statement.
Notify me controls which credit alerts reach your own inbox: a warning when the allocation is spent (on by default), and an optional early heads-up at 50%, 75%, 80%, or 90%. Each admin sets these for themselves.

​
How Teammates Join

New teammates sign in with their organization work email through your identity provider (Google, Microsoft, or SSO). After their first sign-in they appear in the roster automatically. Share your organization’s ProDex URL with them directly — the platform does not send invitation emails.
Enrollment policy (who is allowed to sign in for your organization) is configured with ProDex during onboarding and is not self-service on this page. Contact your ProDex representative to change it.

​
Best Practices

  • Keep at least two admins. If a single admin leaves or loses access, the remaining admin can still manage the team.
  • Review the roster periodically. The Last active column makes it easy to spot users who’ve left the organization; remove them to keep access controlled.
  • Use organization memories for shared knowledge. Company-wide conventions belong in one curated place, not repeated in every factory.
  • Use impersonation for support, sparingly. It’s the fastest way to reproduce what a teammate is seeing without asking them to screen-share.