[Guidance] Ensuring project members have the correct access to the portfolio site

[okms]

Discussion theme music 🎵 Kenny Loggins - Danger Zone

We are receiving feedback that there is still confusion on who needs access where when generating status reports. Some customers have added everyone in their tenant as visitors on the hubsite which in turn will allow the hubsite to be used as navigation, but you cannot write back metadata changes or status reports.

The result of this discussion should be to expand / clarify any recurring issues in the following wiki section
https://github.com/Puzzlepart/prosjektportalen365/wiki#-om-datatilgjengelighet-rettigheter-og-tilganger

Issues for discussion

1. The current documentation implies (but does not directly state) that everyone who is a member of a project, also is a member of the hubsite.

a) Should we clarify this by explisilty stating this point.
b) Does everyone need to be a full member, or does it suffice to have write acceess (contribute access) to the SharePoint site collection. If it is not required to be a full member, can "everyone" be in the visitor group with only project managers, e.g. through a security group, being in the members group.

2. What strategies do we reccomend for maintaining the correct access to the portfolio site?

If everyone needs to be a member, one strategy, while not ideal, would be to have the portfolio site act as a org-wide team with automatic membership.

cc: @pzlespen @tarjeieo @olemp @Remi749