Workfront

StacKr · 12/27/24

My company uses a typeahead field on most of our templates to indicate which client a project is for. The typeahead references our list of Companies. With the Light license, our main users were able to see all companies in this field. I was hoping to move some of them to the Contributor license and the default Contributor access level, but that seems to have disrupted their ability to view other companies. After some experimentation I believe this is linked to having view access to Resource Management, but I don't see any documentation about why that might be.

Does anyone know why this might be occurring, and if it is indeed linked to Resource Management?

TerryHy · 12/27/24

Under the Contributor Access Level, have you already double checked the "Set additional restrictions..." section to see if the settings are correct for viewing companies/groups, etc.

StacKr · 12/30/24

Yes, the only option selected in that section is disabling the AI assistant

KellieGardner · 12/30/24

I tested in my instance and confirmed this behavior. We also had no additional restrictions tied to the access level.

I did change the light access level to no access on resource management and the light license was still able to see the companies, so I don't think it's tied to that. It has to be a permissions-based thing but I just can't find anything on experience league that shows what it is.

Might be something for support to answer?

KatherineLa · 12/31/24

Confirming the same behavior in our instance. I'm going to open a bug report with Support on it. There's no way they intentionally put a single typeahead field behind a paywall to require us to convert hundreds of users to paid licenses on purpose, I'm sure. Hopefully it will be fixed quickly, or my instance is going to come off the rails real quickly in a couple days. That type of field is crucial in almost all of our request queues.

KellieGardner · 1/2/25

Curious what you'll find out. The new licensing model always seems to reveal something interesting.

StacKr · 1/3/25

Agreed. This is really throwing a wrench in our license management. If we have to build a workaround for typeahead fields, it would require a lot of extra time to recreate a feature that already exists.

KellieGardner · 1/3/25

@StacKr - Were you able to connect with support on your issue to ask?

KatherineLa · 1/7/25

I've done some recordings for Support from our instance, and demonstrated a proof-of-concept for how I will use external lookup fields to circumvent the bug/security issue if necessary. Hopefully they will be able to address this quickly.