...
To have correct permissions on portals we also recommend to update or reset pkgroletemplate instances and all the other pkg* objects. If you pkgroletemplate instances (steps to update below)
If you need to reset your permissions from the nar, don’t forget to call the update (admin) endpoint given by PACKAGED_Security.
A touch on the users may also be needed to ensure that users, roles and roles templates are correctly synchronized.
| Info |
|---|
For the portals to be fully functionnal, and to benefit from the “share” feature fully, the “update” endpoint will add a new instance instances in pkgsecugroup & pkgsecupermission, to allow users to access public portals and their assets without being logged in (direct access by link). |
If you can’t reset your permissions, you must modify them. You can do this by using wedia-config’s config’s role template menu. For each role template, you will edit it’s “ Global permissions ” permissions.
...
Disable PACKAGED_Portals
In your front app’s feature config, set portals to false
Deactivate all permissions to portals feature from wedia-config
4/ Configuration possibilites
...
After this update, the user will only be able to see portals that share the same organization as their own.
4.4/ Permissions
Guillaume LEPICARD Alioune Badara CAMARA Peut-être ce point n’est pas nécessaireAs explained above (https://crossmedia.atlassian.net/wiki/spaces/WD/pages/edit-v2/3298787349#1.1%2F-Permissions) you can edit portal’s feature permissions from wedia-config under the “Global permissions” menu.
4.5/ Public Sharing Activation/Deactivation
...