Overview
The Team page is an admin-only section for managing your organization’s team members and enrollment policy. If you’re an admin, you’ll see it above Settings at the bottom of the sidebar. Members don’t see the Team page — they only see Settings. If a member needs an invite sent or a role changed, they should reach out to an admin on their team.For the full Member vs. Admin capability comparison, see First Login: Your Account. This page covers the admin workflows for managing the team.
Getting Started for New Admins
- Check your enrollment mode — decide whether anyone with your organization’s email domain can join (Open) or whether you want to approve each member individually (Invite Only). Invite Only is the default.
- Set the default role that new members receive automatically. Member is the default; change it to Admin only if you want new joiners to have full team management permissions.
- Invite your team. In Invite Only mode, add each person’s email to the allowlist, then share your organization’s ProDex sign-in URL with them directly — the platform does not send an invitation email automatically. In Open mode, just share the URL; anyone with a matching email domain can sign in.
- Review the roster after your team has joined. Confirm each person has the right role and adjust any that need to change — role changes take effect immediately.
Page Layout
The Team page has two sections:- Organization settings at the top — enrollment mode and default role
- Team roster below — the list of all users in your organization
Enrollment Mode
Controls how new users join your organization.| Mode | Behavior |
|---|---|
| Open | Anyone with an allowed email domain can join by signing in with their work email. No admin action needed per user. |
| Invite Only | Only pre-approved email addresses can join. Admins add emails to an allowlist before the user can sign in. This is the default. |
Default Role
When a new member joins — whether through open enrollment or an invite — they’re assigned this role automatically. The default is Member (full access to build, run, and analyze — but not to manage the team). Admins can change the default role to match their organization’s policy. If you change the default to Admin, every new member gets admin privileges on first login.Roles at a Glance
| Capability | Member | Admin |
|---|---|---|
| Build models, run simulations, create experiments | Yes | Yes |
| Configure BOMs, pipelines, plans | Yes | Yes |
| Use Dexter (all capabilities) | Yes | Yes |
| Create and manage factories | Yes | Yes |
| Manage team members and invites | No | Yes |
| Change enrollment mode and default role | No | Yes |
| Manage organization memories | No | Yes |
Team Roster
The Team page lists every user in the organization with:- Email — the user’s work email
- Role — Member or Admin, changeable via the dropdown
- Joined — the date the user first signed in
- Actions — remove the user from the organization
Changing a Role
Click the role dropdown next to a user’s name to promote them to Admin or demote them to Member. The change takes effect on their next page load.There’s no limit to how many admins an organization can have. At least one admin must exist at all times — you can’t demote the last admin.
Removing a Member
Click the remove icon in the Actions column to remove a user from the organization. Removed users lose access to the ProDex workspace immediately.Removed users’ data is preserved, not deleted. When a user is removed, their account is deactivated and their factories, conversations, memories, and uploaded files are retained server-side. An admin can re-add the user later to restore their access and all previous work. The user does not start fresh — their factories and Dexter context are recovered as they were.
Inviting New Members
How you add new members depends on the enrollment mode:Invite Only Mode
- On the Team page, enter the email address you want to invite
- Click Add — the email is added to the allowlist
- Share the ProDex URL with the person
- When they sign in with that email (via Google, Microsoft, or SSO), their account is created and they’re assigned the default role
Open Mode
No admin action needed. Anyone with a matching email domain can sign in directly. Share the ProDex URL and they’ll be enrolled automatically on first login.Relationship to Other Features
Settings vs. Team — Settings holds per-user preferences (appearance, canvas options, Dexter behavior). The Team page holds organization-wide configuration (enrollment, roles, membership). Members see Settings; admins see both. Factories — Factories are personal, not team-shared. Team membership controls who can log in and use the platform, but each user’s factories are private. Even admins can’t see other users’ factories. Organization Memories — Organization memories are shared knowledge that admins curate for the entire team — glossaries, process conventions, standard rules, or any operational context that should be consistent across the organization. Only admins can create and edit them; members can read them but not change them. Dexter consults organization memories in every factory across your organization, so anything you capture here shapes how Dexter works for every team member — making them the right place for institutional knowledge you want applied consistently. Manage them through Dexter’s Memories panel.Best Practices
- Start with Invite Only. It’s the safer default — you control exactly who has access. Switch to Open only when you’ve confirmed that domain-wide access is appropriate.
- Keep at least two admins. If a single admin leaves the organization or loses access, the remaining admin can manage the team. With only one admin, you’d need to contact ProDex support.
- Export before removing as a precaution. While removed users’ data is preserved and can be restored by re-adding them, exporting important factories before removing a team member is still good practice.
- Review the roster periodically. Users who’ve left the organization may still have active accounts. Remove them to keep the workspace clean and access controlled.
- Use organization memories for shared knowledge. Instead of each team member teaching Dexter the same things in their own factories, have an admin set up organization memories for company-wide conventions, terminology, and operational rules.