Feature ideas

I want offer my end users the ability to invoke a Port self-service action at the end of their gitlab pipelines, but sharing around a superuser clientID and secret doesn't feel great.

I want offer my end users the ability to invoke a Port self-service action at the end of their gitlab pipelines, but sharing around a superuser clientID and secret doesn't feel great.

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.

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).

Hello PORT Team, We have a case where our component, Octopus, is accessed by PORT via an API. Since this is an external request, we are required to implement RBAC (Role-Based Access Control), meaning that every request must generate a JWT. Practically, what we need is to perform a request to obtain the JWT before each SSA action and then include it in the header of the action.

Sometimes there is a need to create multiple Port "Workspaces", for example, for staging and prod versions of Port. We would like to add the ability to create several workspaces to an organization and to be able to easily switch between them via Port's UI.

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

Today you can add additional filters via JSON to any table, chart, etc using some of the intrinsic functions like: "getUserTeams()". With the ability to customize the user data-model (like a profile), it would be beneficial to access other user data properties to filter on that we added custom. Perhaps a new function like: getUserProperty("myCustomProp") to use in rules: { "property": "github_user_id" "operator": "=", "value": "getUserProperty('my_github_user_id')", }

Managing dynamic permissions requires specific skills and is more challenging to debug and verify. To assist, we want to provide an improved UI that will allow us to test the result and verify users defined the permissions as expected.

We use folders to organize the catalog, and we have a dedicated folders for work-in-progress. Today it is possible to configure permissions only at page level. We would like to be able to control permissions for entire folders as well so that e.g. any page added to the WIP folder will be visible only to Admins