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. Integration Documentation: the notes Dexter reads when working with your integrations
  5. Usage: adoption and activity analytics per member
Members don’t see the Team item — they only see Settings and the other sidebar utilities. 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
  • 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

There’s no limit on how many admins an organization can have, and at least one admin must exist at all times — 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. Role changes apply from the user’s next page load.

​
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 to remove them; you can’t remove yourself. 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 that admins curate for the entire team: glossaries, process conventions, standing rules, or any operational context that should be consistent across the organization. Dexter reads them as background context in every factory in your organization, so anything captured here shapes how Dexter works for every member. Create and edit them from the Admin Panel with New File. 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.

​
Integration Documentation

When your organization has integrations configured, this section holds the documentation Dexter reads when working with each one. Admins can edit these notes to steer how Dexter uses an integration; connection details and credentials are managed separately. If nothing is configured, the section reads “No integrations are configured for this tenant.”

​
Usage

The Usage section shows adoption at a glance for a rolling window:
  • Summary tiles: members active in the last 7 days, active in the last 30 days, inactive for more than 30 days, and never active
  • Per-user table: last seen in app, last AI call, session count, AI call count, and total active time
Use it to spot teammates who haven’t picked up the platform yet, or to see where Dexter usage is concentrated.

​
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.