Feature ideas

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')", }

Manage your users and teams the same way as all your blueprints! This will enable you to: Add additional properties to teams and users Create relations between user, team, and any other blueprint See teams and users as part of your relations graph

The initial Port implementation of SCIM does not include support for Google Workspace. It would be good if it was included.

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.

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

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

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

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.

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.

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.