In October’s update, we’re rolling out improvements to make your workflows smoother and give your team better control over development.

Now, new entries in tables are hidden by default to help you focus on the data that matters most. We’ve also made it easier to edit and copy entries in tables, and the updated property dropdown makes finding and selecting custom properties simpler. Plus, we’ve added a new integration with Orca Security and enhanced other integrations.

New properties are now hidden by default in all tables referencing a blueprint. Properties are only added to the specific table where they’re created or explicitly selected, giving you more control and ensuring you see only relevant information.

We're excited to share a small but impactful update to our tables! The edit and copy buttons now appear directly over the existing text on hover, removing unnecessary whitespace. This update keeps your data visible and accessible, so you can make adjustments quickly and intuitively.

Customizing your experience with in-house properties? Now, it is easier to discover your next custom property with the new properties dropdown and categories. This enhancement supports teams in tailoring Port to fit specific needs, making property management more intuitive and organized.

As autumn settles in, we're excited to bring you fresh updates from Port. This month, we've made tracking simpler than ever, helping your teams measure performance and enhance delivery practices. We've also introduced to make your action forms easier to fill out, improving the user experience when completing forms. But that's not all—there's more to explore. Dive in to discover all the new features we've rolled out!

📊

We made it simpler than ever to track DORA metrics in Port! DORA metrics help teams measure their performance and improve delivery practices. Our new guide walks you through setting up and tracking these metrics using your existing tools and processes.

Check out the guide here!

🧑‍💻

We’ve streamlined the self-service developer experience by introducing . Now, you can group complex forms into easily manageable steps, making action forms more intuitive and efficient for your team.

Learn more in the docs.

🔐

Build your custom automated workflows integrating with any API directly with in Port! Secrets are securely stored and can now be referenced in your custom actions and automations using .

Use this feature with the Webhook invocation method to create automations, seamlessly integrating with any internal or external tools in your stack. For example, See how our own platform team implemented "Page the on-call" action via PagerDuty with no-code.

For more details, check out [the docs](https://docs.getport.io/sso-rbac/port-secrets/

🤖

are non-human users (bots) that you can use to integrate external tools and automate daily tasks in Port.

You can now leverage Port's robust RBAC system by using them. Associate Service Accounts with teams and roles, or mention them directly in permission settings, just like any other user. This means you can securely automate tasks and workflows while maintaining precise control over permissions.

See the docs to learn more.

Note: (currently in beta) is required to use this feature. Learn more on Users and Teams and how to enable it.

You can now seamlessly integrate your Port service catalog with Incident.io, enabling better incident tracking and management. Sync your service entities effortlessly to enhance visibility and streamline your incident response process.

Happy end of summer with new release notes from Port. In this edition, we’re continuing to make automations more impactful, with workflows, making it easier to build in Port with guides and adding various capabilities in the creation of the data model and syncing data.

🔗

You can now create and trigger multi-step workflows within your developer portal, resulting in advanced automations that chain actions together.

You can choose different automation triggers, such as the status of other actions, Port API, or chain external services.

Check for examples in our Docs.

📖

Explore our updated Guides section for easier access to tutorials and documentation. You can filter guides by use cases, portal functionality, and technologies to find relevant content faster.

Parse specific GitLab metadata content and add it as metadata into the Port software catalog. For example, you can extract dependencies from for better visibility or use files to map services to their owners in the Portal. This capability already exists in GitHub. See Docs.

You can now update entities by looking up their properties and not just by their identifiers. For example, when enriching entities like with PagerDuty data, you can use a known property (e.g., ) to update the relevant data.

This feature is supported across all integrations and the Port API. This reduces the need for multiple blueprints and mirror properties and simplifies catalog ingestion. See Docs.

Easily track the status of your data syncs and keep your catalog current. You can now see when a sync is in progress, when the last sync occurred, and when the next one is scheduled (for integrations with a defined resync schedule).

We've also added a "Resync Now" button on the integration card, allowing you to manually trigger a sync.

We've introduced a new widget type that lets you display the details of a specific entity within your dashboards. For instance, you can showcase team entity details directly on a Team page or display environment details on a monitoring dashboard, providing users with a more focused and relevant view.

Check our Demo.

↕️

You can now define sorting for entities in the action input form, making it easier for developers to find and select the relevant entities. See Docs.

You can now sync deployment data from Octopus Deploy into your Port catalog. This integration helps you keep track of deployments and environments, enhancing visibility and control over your deployment processes. See Docs.

You can now generate direct links to specific self-service actions in Port, allowing users to access them immediately without navigating through the portal. This is perfect for sharing in Slack channels or internal documents to streamline workflows and enhance accessibility.

We've refined the quick menu to make actions more accessible outside of the menu itself. Now, you can access available actions directly from the table view without needing to open the quick menu, making it faster and easier to interact with entities.

How are you spending your summer? We’re spending it on making Port better, notably by releasing Port-hosted integrations, which make it simpler to set up Port.

🌊

We are extremely excited to announce the release of "Hosted by Port" Ocean integrations! 🔌 🌊 plug-and-play, installed within minutes, and doesn't require any maintenance on your side.

These integrations come with portal templates. Once you connect them, you will already have a basic internal developer portal, ensuring you’re ready to run and do not have to worry about data models in the initial phase.

To install, choose the "Hosted by Port" installation method when choosing a new data source in the "Data Sources" section of the Builder area.

Managed integrations will be displayed with a "Hosted by Port" tag. See docs.

💾

Table views are now persistent so that any portal user can create their own views and filters. Views will be saved for future visits and can be shared as URLs to collaborate with colleagues. This makes using the portal simpler and more personal for your users. See docs

💬

Leverage the new “Send Slack message” action type to easily define and drive automatic notifications in Slack, such as alerts or nudges on action items that are past their due date. See docs.

You can now manage the Port integration with multiple AWS, Azure or GCP accounts in one place, saving you time on copy-pasting configurations and settings. See docs for AWS, Azure and GCP.

You can now use the Port API natively as part of Actions and Automations, allowing you to execute any Port API route you wish with automatic authentication. This is helpful to automate actions that result in changes inside the portal. See docs.

The biggest theme for our first 2024 summer release notes is using the portal for engineering insights. Portals are a natural place to understand everything about the engineering organization: its productivity, agility and standards compliance. This is a result of the fact that the portal is a single source of truth about teams, developers, services and infrastructure and the relationships between them. This new software engineering intelligence capability makes Port more useful to engineering leaders, especially since Port doesn’t just provide insights, but also the power to change behavior, productivity and standards compliance.

Port now supports tracking and visualization of historical data. This is ideal for a variety of what’s called “software engineering intelligence” needs, such as DORA and other engineering productivity metrics, and also useful for any work on standards compliance. We’re thinking of calling this set of capabilities “insights” 💡. Practically you can use it as a line chart widget that displays the history of number properties as trends. Line charts can also visualize the history of aggregation and calculation properties to create a bird's-eye view of custom metrics, like:

See docs to learn more.

Bring GitOps to life with json and yaml mapping, enriching your catalog with any data you already have in your repositories:

1. Use JQ to map specific fields to your catalog entities. For example, map the “package manager” from a package.json file to a service entity

2. Create and update multiple entities based on arrays in files. For example, map all dependencies from a package.json as an entity per dependency

See docs to learn how to map file content from GitHub

You can now require more than one approval for an action to be completed, for cases that require multiple approvals. All approvers will get notified for approval and can add a note explaining their decision. See docs to learn more.

When defining relations as part of integration mapping, you can now define the relation using a comparison with any entity property instead of just the identifier. See docs

You can new enforce view permission for entities according to roles, users, specific teams, or dynamic team ownership, which will take effect both on the Port app and when interacting with the API. See docs

We added a live examples capability when testing the mapping for K8s, GitHub and BitBucket exporters to make the mapping experience much easier

Mirror and view multiple related entities and their properties.

You can now use entity details for context when defining automations based on their timer expiration trigger. Learn more on how to use trigger context in automations

These release notes mark a significant milestone for Port: automations. Ever since we began developing Port, we knew that the software catalog is at the core of the portal, that it is real-time, and that it contains important context other tools don’t have. The next logical step was leveraging this power for automations, which were possible in Port but complex. These release notes contain the automations feature. It is meant to help you realize the power of the portal. Stay tuned: we have more to do on the automations front, and we will.

⚡️

We are excited to unveil our new Automations feature, designed to streamline and enhance your developer workflows. Automations allow you to automatically trigger workflows, alerts, and notifications based on changes within the software catalog, such as a new entity being created, a timer that expired, a scorecard change, or any other change in existing entity data. See docs to learn how to set up your first automation.

🌊

integration is now better, allowing you to display an accurate, real-time representation of your AWS resources as part of your software catalog and customize the integration in Port. See docs.

With the new integration, you can import monitors (also known as alerts), SLOs, and services from your Datadog account into the Port software catalog. See docs.

🚥

You can now define custom levels and colors for scorecards. For example, you can use levels with stoplight colors. See docs.

Creating and tweaking how data sources map to your software catalog is now a much better experience, as we introduced a playground to test your mapping on real examples. See docs.

As an API-first company, we are proud of our API and its capabilities. Today, we improved our API Reference so you can explore, learn, and test the API routes more efficiently than ever. Visit the new API docs

You can now apply filters and conditions to day-2 actions so that they appear only on the relevant entity actions list. See docs.

You can now delete entities using a webhook integration definition. See docs.

We improved the order in which global search results appear, making it easier to find what you need. See docs

You can now rotate your Port organization secret/s using the UI or the API. See docs

As part of the automation feature, we added an invocation method to create or update entities in the software catalog based on the automation context or user inputs. This is useful for automating changes based on events in the software catalog or creating self-service actions to update specific properties of an entity utilizing RBAC for self-service actions. See docs.

Our biggest news this month is the GCP integration, allowing you to see all GCP resources in the portal, in context of any other software catalog entity. We’ve also worked on many usability improvements, and added a handy automation feature.

In other news, we also released a simple tool to help you plan your portal roadmap as part of our portal-as-product approach. You can access it here.

You can now ingest Google Cloud resources into the software catalog, including projects, container clusters, cloud-run services, BigQuery tables, compute engine autoscaler, and other GCP objects. The integration with GCP supports real-time event processing, which allows for an accurate real-time representation of your Google Cloud infrastructure inside Port. See docs.

✏️

You can now create custom payloads when setting up actions. You can use it to set up self-service actions that can directly connect to existing APIs or pipelines without the need to make adjustments in a separate step. See docs.

In the builder tab, we made working on the data model easier:

You can now display a specific entity’s number property in any dashboard with the number chart. For example, get an MTTR metric for a service directly from PagerDuty and display it on the specific entity dashboard. See docs.

You can now set an automated workflow by triggering actions automatically on behalf of users. These actions will show up for users on their “my actions” panels. See docs

It’s springtime, and along with the new flowers, leaves and the natural beauty of the season, Port re-branded. In case you haven’t noticed, check out the Port site or your Port developer portal. We also invested in letting you create personalized places for developers where they can easily see what needs to be done, and similar experiences for platform engineers modifying the data model.

↘️

We're excited to unveil Port's fresh rebranding. Here’s to our designers Val Burtakov and Ory Zydner, for better expressing what Port is all about, and creating a site and brand that we really love. Have a look.

🗒️

Instead of working in the builder section of the portal, platform engineers can now make changes to the data model directly in the software catalog. You can now add and edit properties in catalog tables, making data model changes easy and immediately seeing how the changes will be seen by developers.

With the new “Action Card” widget, you can now add self-service actions to your dashboards within its context, creating a holistic developer experience. For example, add a “Rollback Service” action to an incident management dashboard. This reduces context switching and helps make any insight immediately actionable. You can display one or more actions in one widget. Learn more.

You can now download a specific table view as a CSV or JSON file for further use.

We’ve added a new sidebar search so you can easily find the catalog page you need.

Create and update entities based on any array in an incoming event. Learn more

The Gitlab Ocean integration now allows the creation of webhooks on specific groups and choosing which branch to listen to.

The biggest item in February’s release notes is Folders. Folders play a key role in realizing our portal-as-product approach, since they allow platform engineers to provide the right experience by developer, team, and manager. Folders let you group portal elements in a way that makes immediate sense to users and only provide them with what they need for a given use case. Additional items this month also focus on improving portal experiences, from the ability to add page and dashboard descriptions to action run status labels.

📁

We are excited to announce the release of folders!

🔌

This Ocean-powered integration makes it easier to integrate Azure DevOps by adding Projects, Repositories, Pull requests, Repository policies, Pipelines, Teams and Members to your catalog. Learn more.

---------------------------------------------------------

You can now view live event logs coming from Ocean integrations. These events contain valuable details for debugging your integration, such as the current status of the ocean container, resync process, and integration startup.

The new event log view is available for all Ocean integrations on the “Data sources” page.

You can now add a custom label to the action run status to reflect any step in the action process. These will be shown as part of the action run status card panel. Learn more.

Add descriptions to pages and dashboards to make them easier to understand and search. Descriptions can be added when creating or editing the page or using the API.

---------------------------------------------------------

When testing JQ expression for a new calculation property, you can now load an existing entity example to test with real scenarios.

See changes in actions and scorecards definitions using the Audit Log page.

For a better user form experience, we now support a toggle form input type. Note that “Select” input type is still available for cases where more than True/False is needed.

You can now configure page permissions with IaC. See docs for Terraform or Pulumi.

visualize your CI/CD pipelines by adding views for Jenkins jobs, builds, and users. Install integration here. See docs here.

provide developers and security engineers with a centralized view of their Wiz controls and issues. Install integration here. See docs here.

--------------------------------------------

Use these actions to create self-service actions for your developers - provision Azure resources, trigger Datadog incidents

--------------------------------------------

To make it easy to debug issues when writing JQ, we now display JQ error messages when trying to test or save invalid JQ.

The table “free search” capability has improved and now supports searching each word separately instead of the entire search term.

When creating/editing self-service actions, you can now switch to “JSON mode” instead of the editing form.

We enhanced the Terraform provider by adding support for - aggregation properties, and the “required” JQ setting for self-service actions.

In order to create a more seamless experience for Port Members, the "Builder" tab is now hidden for them.