Feature ideas

Introduce support for service accounts within Port to enable automated, non-human access to the platform for integration, automation, and management purposes. This feature would allow systems and services to interact with Port directly, facilitating seamless workflows and enhancing operational efficiency.

Right now there is no way to create an access token for another user. This is necessary when some operation (i.e. GitHub action) needs to trigger for example a self-service action on behalf of some user.

Currently the teamsIdentifier, and teams arrays are not available in the user context in Self Service action dynamic permissions. For example, if you want to use "{{.user.teamsIdentifier}}" or "{{.user.teams[].name}}" as a value in a dynamic permissions policy, you can't do that as those values aren't present on the .user object in the dynamic permissions/self service action context.

In addition to the ability to create personalized pages and expose them to users via the web UI, we would like to allow defined permissions to view specific entities, which will be enforced in the UI and API (when users are trying to access specific entities outside of the web UI)

Ability to assign permissions according to the data model you defined for your organization. How it will work: When assigning permission (for example, to execute an action), the new capability will allow to query the catalog entities and create a permission condition based on the queries. For example: Allowing a developer to execute the "Deploy" action only if the developer is related to the same domain as the service Allowing a user to execute the "Lock/unlock deployments" action only if the user appears in the catalog as the "team leader" of that service The first version will support assigning dynamic permission for executing an action, in the future we will add the support for editing entities.

Admins can now create teams in Port and assign users to them. It’s done via the “Teams” tab on the “Users & Teams” page. You can use teams to represent the software and infrastructure owners in your organization. For example, “Frontend team” and “Backend team”. You can also add a team description of your choosing. When you assign a user to a team, they will be able to see what software assets they own and are responsible for. In addition, they will be able to view and perform actions on their assets, according to their role and the team they belong to.

You can now see full details about a user or a team on their dedicated profile page. That way, you have a clear view of what assets each user/team owns. To do so, click on the desired user/team name. The profile includes general details such as user info, email, role, status, and team, and s list of entities the user/team is responsible for.