Skip to main content
Solved

"*" now longer allowed as a Person ID - access for all users

  • November 6, 2025
  • 2 replies
  • 37 views
E
Do Gooder (Employee)
Forum|alt.badge.img+3
  • EDPIUS
  • Do Gooder (Employee)
  • 6 replies

Objective: Access Template that gives view access to all users

The solution to this used to be to create an Access Template with the Person ID = *

This worked so long as * was not the person ID for the appowner, IFSAPP. (Easy solution: make a new person ID = IFSAPP and associate it with the user IFSAPP.)

However, when a customer using Cloud 24R2 SU8 tried to do this, there was an error message that * is not allowed as a Person ID; no mention about appowner, just that * is not allowed at all.

If that’s the case, what is the solution for this common business requirement.

Thanks

Best answer by matt.watters

Hi Edwin,

I have not seen any issue with putting Person * on an Access Template in any releases of Cloud that I have worked in.

  • Person * should not be connected to any User ID.
  • Person * cannot be added to a Person Group. I think this has been true forever

Could there be a customization in place preventing this?

    2 replies

    matt.watters
    Ultimate Hero (Partner)
    Forum|alt.badge.img+26
    • matt.watters
    • Ultimate Hero (Partner)
    • 699 replies
    • Answer
    • November 6, 2025

    Hi Edwin,

    I have not seen any issue with putting Person * on an Access Template in any releases of Cloud that I have worked in.

    • Person * should not be connected to any User ID.
    • Person * cannot be added to a Person Group. I think this has been true forever

    Could there be a customization in place preventing this?

    If a response resolves your issue, please use "Best Answer" so that the thread can be closed and others can find solutions more easily. Regards - Matt
    E
    Do Gooder (Employee)
    Forum|alt.badge.img+3
    • EDPIUS
    • Author
    • Do Gooder (Employee)
    • 6 replies
    • November 7, 2025

    Thanks, Matt.

    My mistake was putting Person ID = * on the Person Group, rather than directly in the Access Template. Once I did that, it worked as expected.

    To others: remember that you must disassociated * with the (default) user ID of IFSAPP. (I have never understood why that is the default for the user IFSAPP, rather than making a person ID of IFSAPP to match.)


    Terms & ConditionsCookie settingsAccessibility statement