Skip to main content

Dazos Administrator User Missing from BD Rep Dropdown (CRM)

Overview Following a recent platform update, the Dazos Administrator user profile was intentionally removed from standard user dropdown menus across the CRM — including the BD Rep field in Intake Opportunities.

This article explains what changed, who is affected, and what steps to take to restore your workflows, reports, and dashboards.


What Changed and Why

As part of a platform security update, the Dazos Administrator profile is no longer visible or selectable by non-admin users in CRM dropdown fields such as BD Rep.

  • Admin users can still see and select the Dazos Administrator profile in dropdown fields.

  • Non-admin users will no longer see the Dazos Administrator option in any user picklist or dropdown.

  • This change applies across all modules and layouts where user selection fields are used, including Intake Opportunities.

⚠️ This behavior cannot be reversed. The removal of the Dazos Administrator profile from standard user dropdowns is an intentional, permanent platform change.


Who Is Affected

Your team will be impacted if any of the following were built using Dazos Administrator as a user reference:

  • BD Rep field assignments on Intake Opportunity records

  • Automated workflows triggered by or filtered on the Dazos Administrator user

  • Reports and dashboards that include Dazos Administrator as a filter or grouping condition

  • Any other CRM field or view that references Dazos Administrator as a selected user

Recommended Workaround

The recommended solution is to replace all references to Dazos Administrator with a different active user or a dedicated placeholder user (for example, a user named CTM or similar).


Step 1: Identify a Replacement User

Choose an active user in your CRM to serve as the new placeholder. This should be a standard, non-admin user account that all staff roles can see and select in dropdown fields.


Step 2: Request a Mass Reassignment from Dazos Support

If you have a large number of records linked to Dazos Administrator, Dazos Support can perform a backend mass reassignment to update all affected records at once.

  1. Contact Dazos Support and provide the username you want to use as the replacement (e.g., CTM).

  2. Support will initiate the mass edit to transfer all records previously assigned to Dazos Administrator over to the replacement user.

  3. Support will confirm once the reassignment is complete so you can verify the changes on your end.

💡 Tip: If your organization has thousands of records linked to Dazos Administrator, a backend mass reassignment is the fastest and most reliable option. Do not attempt to manually update records one by one.


Step 3: Update Workflows

After records have been reassigned, manually review and update any automated workflows that reference Dazos Administrator as a condition, trigger, or assigned user. Replace each instance with your chosen replacement user.


Step 4: Update Reports and Dashboards

Review all reports and dashboards that use Dazos Administrator as a filter or grouping. Update each one to reference your replacement user so that data continues to display correctly.


Tips & Notes

⚠️ Re-enabling the profile globally will not fix the issue for non-admin users. Even if the Dazos Administrator account is active in the global Users list, it will still be hidden from standard (non-admin) user dropdowns. The platform change controls visibility by user role, not by account status.


Best Practice: Avoid using administrative system accounts as workflow or reporting placeholders. Instead, create a dedicated placeholder user with a standard role to ensure consistent visibility for all staff.


When to Contact Support

Reach out to Dazos Support if you need assistance with:

  • Performing a backend mass reassignment of records from Dazos Administrator to a replacement user

  • Confirming which records are still linked to the Dazos Administrator profile

  • Any unexpected behavior after completing the steps above

Related Resources

Did this answer your question?