...
To have correct permissions on portals we also recommend to update pkgroletemplate instances (steps to update below).
If you need can afford 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 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 role template menu. For each role template, you will edit it’s “ Global permissions ” permissions.
For the “Administrator role type” the permissions should be configured this way :
Create portals => checked ✅
Administering portals => checked ✅
For the “Contributor role type” the permissions should be configured this way :
Create portals => checked ✅
Administering portals => not checked 🟩
For the “Userrole type” the permissions should be configured this way :
Create portals => not checked 🟩
Administering portals => not checked 🟩
...
manually, to do this, you will have to check the differences (diffs) in the new role templates, which can be found in the upgrade guide linked here. => https://crossmedia.atlassian.net/wiki/spaces/WD/pages/3181936642/Upgrading+to+2024.4#pkgroletemplate
After this, call the update endpoint to retrieve the new pkgsecugroup and pkgsecupermission instances.
1.2/ Front app
You will also need to upgrade your portal to retrieve all the new components and configs to benefit from the portals
...
Add a property
organization, which is a child oforganization, touserstructure. This property should have the tagsegmenting/tree/readorgs.Add a property
organization, which is a child oforganization, toportalstructure. This property should have the tagsegmented/readorgs.portalstructure should have the tagsegmented.organizationstructure should have the tagsegmentedFYI: "readorgs" is just an alias here. It can be any name you choose, but it must be the same on both properties for the segmentation to work correctly.
After this update, the user will only be able to see portals that share the same organization as their own.
4.4/ Permissions
...
should have the tag
segmented/readorgs.portalstructure should have the tagsegmented.organizationstructure should have the tagsegmentedFYI: "readorgs" is just an alias here. It can be any name you choose, but it must be the same on both properties for the segmentation to work correctly.
After this update, the user will only be able to see portals that share the same organization as their own.
4.4/ Permissions
You can edit portal’s feature permissions from wedia-config under the “Global permissions” menu.
For each role template, you will edit it’s “Global permissions” permissions, here you'll find the settings that are set by default.
For the “Administrator role type” the permissions should be configured this way :
Create portals => checked ✅
Administering portals => checked ✅
For the “Contributor role type” the permissions should be configured this way :
Create portals => checked ✅
Administering portals => not checked 🟩
For the “Userrole type” the permissions should be configured this way :
Create portals => not checked 🟩
Administering portals => not checked 🟩
4.5/ Share privacies configuration
It is possible to configure the different types of visibilities that will be displayed inside the Share Portal modal.
...
That configuration can be specified via the configuration entry point: starter-kit/portals/share-options[].
For example, to remove the ability to set a portal as Public in the front-end, the visibility entry that has the type “public“ can be deleted from the base configuration array $.portals.shareOptions[].
This selection will control the value of the property visibility and the portal isntance will be updated accordingly (See the 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
Alioune Badara CAMARA 3299180556/Portals+feature+explained#Visibility for more details).
4.6/ Searching for a Portal through the DAM
...