Centralize user and team data for streamlined automation and software ownership tracking

Users and teams are perhaps the most essential cog in developing and delivering great software, so Port is giving them the first-class treatment they deserve. We’re pleased to announce that one of our most requested features — the ability to customize users and teams to fit your company’s unique structure — is now available in Port! 

Rather than prescribe a rigid definition of a user and team, or perhaps import one from an authentication tool, you can now use Port’s blueprints to model your users and teams however you desire. 

It’s common for user data to be scattered across several tools. Authentication details from one source, a GitHub ID, an Atlassian ID, a Slack account or maybe several. Teams are similar: there’s the management hierarchy, but engineering teams might group together on a project. There could be domain experts, dedicated project and team communications channels. Using Port blueprints, you can gather all this information in one place and use it to make Port work the way your teams do.

Note: User and Team blueprints will be required for all Port users starting 1 May 2025. If you created your Port instance prior to 14 January 2025, you will need to perform a migration prior to 1 May to ensure smooth operations. If you created your Port account after 15 January  2025, you already have the User and Team blueprints feature and no additional steps are required. 

Flexible structures for unique organizations

Your internal developer portal is meant to be the source of truth about your software and the teams that create and manage it, across all the tools in your software lifecycle. Blueprints in Port describe the data you want inside your software catalog and also the relationships between items. With user and team blueprints in Port, you can capture all the relevant metadata you need about the people in your portal, which in turn enables powerful automations and workflows, as well as clear ownership and visibility throughout your SDLC. 

This innovative approach enables organizations to add layers of custom properties to users and teams, creating intricate networks of relationships that extend beyond traditional boundaries. In the first figure below, users in Port have the usual details like email addresses and names, and they’re linked to authentication systems. But we’ve included additional details like language and security expertise, and functional roles. We could add in their GitHub ID and Slack handle, details about their use of an AI coding tool – really anything we want.

‍

In the second figure, we’ve configured our teams. Here we’ve pulled in Slack channel info, a team’s design board in Figma, and details across several Atlassian tools. We’re also aggregating specific data on each team like their GitHub Copilot usage stats and several engineering metrics.

‍

Start your journey toward smarter team management today! 

New to Port? Explore our demo or sign up for a free Port account and start using the new Users and Team blueprints today. More details are available in the Port docs.

Signed up for Port before 15 January 2025? 

On 1 May 2025 this blueprint approach will be the default for everyone, so we encourage existing users to begin their migration plans and to reach out to us if you have any questions. Migration is also required if you were using the beta version of the user and team blueprints.