Forum Discussion
SharePoint Access Requests Settings
This may be a disconnect for me: when I look at the groups (which is via TEAMS), I don't see a 'Group administrators' role as you mentioned. All I see are the TEAM's Owners and Members. Where can I find the additional group's administrators listed?
Open the SPO Site, click the Settings Gear for the site (between the Bell and the ?) then choose Site Permissions this will take you to the SharePoint permission page that provides sharepoint specific capabilities.
- When a SPO site is Group enabled, the accounts that are assigned to the Owner role within the associated Office/AAD group become SCAs due to the fact that the Office group is assigned to the SCA role in SPO. While the entire group is assigned to the SCA role, their is some code running in the background that prevents the Members of the group from performing tasks that should only be done by the SCA.
Associating a site to a Hub does not affect security. This can become a problem if the Hub Site owner does not have access to a linked site. This needs to be manually coordinated.
in this approach Group Owners are also Site Owner as well as SCAs, which demonstrates the need to have a good Group Management strategy. Groups can easily get orphaned when a single owner leaves and the only way to prevent this is to have some custom scripts running.
Don't create separate DLs, that will just make things more confusing 🙂 Thanks Dean_Gross
I have checked that, however, I'm under the impression that Site Collection Admins and the "Admins" designated in the Access Request settings when the site is teamified, are different since, when the site is not teamified, the reference is to Owners, not Admins.
So, are you saying that the teamified site's reference to 'Admins' in the Access Request Settings is, actually, the Site Collection Admins? If so, this becomes a problem, I believe, when the site is associated with a Hub because then, the Site Collection Admins that receive the requests for access are those of the hub site instead of the site itself. In the delegated world of one-site-per-site-collection that we live in now, the site owners need to be getting the requests, not the Collection Admins, and to set up a separate DL for each site, as a workaround, does not promote self-management or delegation or get IT out of the middle of it. For us anyway, it creates the very bottleneck we're trying to eliminated by using Modern sites, hubs, and group functionality.
Would you please clarify this for me? Thanks.