Can't see templates with profils other than Super-admin

[Skududu]

Hello,

We are using the "Datainjection" plugin with GLPI version 10.0.14. The plugin works correctly for a super-admin, but it is impossible to see the models with the technician profil. The permissions seem to be correctly set for this profile.

Could you help me?

Thanks

[sblanchouin]

Hi,

Same problem !

GLPI 10.0.16
datainjection 2.13.5

Thanks

[stonebuzz]

hi

by default the models created are private

Even if you have create / view / update rights,
this only applies to public models or models created by you.

can you check this option ?

[Skududu]

Visibility is on "public"

[stonebuzz]

Can you check that the entity in which the model is created is accessible to the tech

[Skududu]

The profile does have access to the entity where the model was created

[stonebuzz]

have you validated the model after field/column mapping?

[Skududu]

I don't have the option to validated the model anymore, so it seem to be validated

[Skududu]

Hello, I still have the problem. Do you have any ideas where it could be coming from?

[github-actions]

There has been no activity on this issue for some time and therefore it is considered stale and will be closed automatically in 10 days.

If this issue is related to a bug, please try to reproduce on latest release. If the problem persist, feel free to add a comment to revive this issue.
If it is related to a new feature, please open a topic to discuss with community about this enhancement on suggestion website.

You may also consider taking a subscription to get professionnal support or contact GLPI editor team directly.

[Dayflare]

i have this issue too. The model is public and in the same entity. Even if i give the user super admin the model isn't visible. All created models are only visible for the user which created them. I had to recreate the model for every user.

please reopen the issue as it's still persistent and not fixed.

[stonebuzz]

Hi

The checkRightOnModel() method (line 1273) builds a UNION query that retrieves the item types associated with both the primary model and all of its related mappings and secondary information. It then checks the canCreate() permission for each retrieved item type.

As a result, a technician who does not have permission to create certain lookup objects (such as Location or User, which are referenced by model mappings) is incorrectly denied access to the model itself and cannot view it, even when they have the appropriate permissions on the primary model.

This behavior has been corrected so that access to a model is no longer blocked by create permissions on unrelated lookup item types used only within mappings.

can you check this ?