SecurityRole Rights do not work correcly when users is only added via Team (SecGroup)

(0) Share

Report

Posted on by RV-19021545-0

Hi there

I got a model driven app where the customer wants to add users via entra id security groups.

I created teams (Type SecGroup) and added e.g. BasicUser to the team.

The users do not have securityroles added directly - only via the team.

If the user uses the app everything seems to work fine... add/edit accounts etc. works.

But some things do not:

- BusinessRule which should hide/unhide attributes do not run

- Export to Excel Online for "mass mutation" throws erros:

- adding notifications throws errors:

but when i add the SAME Security Rule directly to the user everything works fine...?

Is this a know bug?

Thanks

Roman

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (2)

Sort by

Verified answer

RV-19021545-0 16 on at

Like
a
(0)

Report
Copy link

Link copied!

- The BusinessRule does work now - it seems it needed Read access to "tour" table.... even when the form does not have to do anything with that table at all.

- Export to Excel works now - import, office document etc. had to be added

- Notifications does work now

Found out via Console mostly.

What I also found out - open question:

There seem to be tables access rights to tables that can not be added via Team directly but have to be added directly to the user.

Saving, Sharing and opening shared Views does not work via Team only.

That seems to be for all tables starting with "user"

Is that correct? Do I really have to add a direct security-role to every damn user then? This makes the usage of Teams with Entra Securit Groups almost useless in my opinion?

Was this reply helpful? Yes No
Scott_itD Community Manager on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @RV-19021545-0 ,

Thanks for coming back and sharing your solution!

I recommend you post your new inquiry as a new question, which will help others in the Community find it more easily.

Was this reply helpful? Yes No
Verified answer

RV-19021545-0 16 on at

Like
a
(0)

Report
Copy link

Link copied!

The problem above has been solved:

The issue was caused by the Setting of "Team privileges only" in the Security Role Settings.

Changing the value to "Direct User (Bais) access level and Team privileges" seemed to do the trick.

The users now only have a security role that is granted via the Team they're part of.

Was this reply helpful? Yes No