Feature ideas

Currently, users can inherit permissions from the groups they belong to, the roles assigned to them, or directly assigned permissions. However, it can be difficult to determine the exact origin of each permission. A page that displays all the permissions assigned to a user, with an additional “Attached By” field, enabling users to quickly identify the source of each permission.

Now, the only way to assign permissions over an entity is by using owning_teams property and configuring the ownedByTeam: true/false on the blueprint permissions. We would like to define custom teams arrays as properties that can be inherited from relations and assigned granular permissions over entities (just like owning_teams, but being custom properties).

Sync groups and roles using the SCIM integration to ease groups management and overall portal permissions.

To define permissions covering that would cover all underlying pages.

Introduce configurable permissions that allow actions to be executed based on specific user data. For example, restrict actions to the current on-call user or to a user who provided a particular answer in a survey. This feature would ensure that actions are performed only by the appropriate users as defined by dynamic criteria.

At the moment you can only rotate the organization secret (from UI and API). Port should also have this ability for the personal secret

Once a service account is created, there is no way to rotate the credentials linked with the service account unless you completely delete the service account and create it again. It would be nice to have either a UI element shown next to the service account that would allow admins to rotate the credentials (similar to how the port client secret already works) or an API to do so.

Have a blueprint to inherit owning teams from multiple blueprints and agregate the teams. I.e. In a model with Application > Project > Portfolio blueprints, Application should be able to inherit ownership from both Project and Portfolio, while Project should be able to inherit from Portfolio while also having its own owning teams (i.e. project may have a 'Managers' team that can manage that project and Applications on it but not the entire Porftolio).

Currently, the SCIM integration operates in the background to ensure secure access to Port. However, it is not fully integrated into the application—provisioning does not add users to Port, and deprovisioning does not remove them. Ideally, the SCIM integration should be fully implemented and seamlessly connected with Port.

As admin users, we have full visibility on everything that's available in Port. We can already control what users see and interact with, but we cannot easily confirm if the changes we have made are correctly tailored to them. It would be very helpful to be able to preview the changes.