tags/notification emails for dummy account | Community
Skip to main content
KristenS_WF
KristenS_WF
Level 7
February 12, 2025
Solved

tags/notification emails for dummy account

  • February 12, 2025
  • 1 reply
  • 479 views

Hi All,

Last year we set up a dummy WF account for our QA team, at their request, so that users could tag the team on notes for various products.  The notification emails from the tag were sent to a shared mailbox to which all the team members have access.

In early January the team manager reported that they were no longer receiving WF email notifications to the shared mailbox (the mailbox does appear to receive non-WF emails).  I looked at the account profile, and the Instant option is turned on for all Communication notifications (and when logging in as the dummy account, I can also see the in-app notifications for tagged notes).  I tested a similar dummy account we use with Fusion, and that account's shared mailbox does receive email notifications (the Fusion dummy account does have SysAdmin rights, but beyond that, it's no different from the QA account).

Our migration to the Adobe Admin Console took place in December (since our IT department left this until the last possible window, I was already out on PTO when the migration took place).  Because of the timing, I suspect the issue stems from something our IT team did/didn't do with regard to this account.  I seem to recall other users reporting issues with dummy/placeholder accounts, but I'm having trouble locating relevant posts.

Have others seen this issue?  To be clear, the dummy user profile still exists; it's just no longer receiving WF notification emails like it did in the past.

Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Kurt_Jones

Matthew, yes, they are shared mail accounts with actual email address (e.g. payments.workfront.support@jpmorgan.com) which I added to adminconsole and provided access to our workfront.  They are not of a real user but maybe my nomenclature of dummy/test wasn't the best context to use.  I will note for our environment we have SSO and every user created in our active directory has a unique ID, even these shared accounts we create.  For us, that unique ID needed to go into the username field instead of email address in order for our stuff to work properly with our SSO.

1 reply

Kurt_Jones
Community Advisor
Kurt_JonesCommunity Advisor
Community Advisor
February 12, 2025

Kristen,

I use dummy/test accounts as well. I did have to get those accounts set up in adminconsole once we moved and assure they had access to our Workfront like any other user account...I'm sure you've done this but just in case...make sure those are also in the adminconsole.

    M
    MatthewLien
    New Member
    March 26, 2025

    Kurt - How did you setup these dummy/test accounts in the Admin Console? Do they have actual emails addresses? We have shared inbox accounts with actual email addresses but are unable to assign them in the Admin Console to Workfront

    Kurt_Jones
    Community Advisor
    Kurt_JonesCommunity AdvisorAccepted solution
    Community Advisor
    March 26, 2025

    Matthew, yes, they are shared mail accounts with actual email address (e.g. payments.workfront.support@jpmorgan.com) which I added to adminconsole and provided access to our workfront.  They are not of a real user but maybe my nomenclature of dummy/test wasn't the best context to use.  I will note for our environment we have SSO and every user created in our active directory has a unique ID, even these shared accounts we create.  For us, that unique ID needed to go into the username field instead of email address in order for our stuff to work properly with our SSO.

      Terms & ConditionsAccessibility statement

      Loading footer...