Skip to main content
All CollectionsCatalogCatalog FAQs
Managing team memberships outside of
Managing team memberships outside of Engineering Team avatar
Written by Engineering Team
Updated over a week ago

Derived attributes in Catalog let you manage team memberships outside of This article will walk you through how to do this with Slack User Groups, but this approach will also work with teams synced via our integrations with:

  • Cortex

  • GitHub

  • Linear

  • OpsLevel

First, you'll need to create a Team type in the catalog if you don't already have one. Once you've done that, edit the type and add a data attribute with type Slack User Group.

You can now add a derived attribute based off of that which pulls in team members via the Slack User Group.

Your team catalog type should now look something like this. You may have more attributes if you already had a team type.

Save your type, and then find or create a new entry and set the "Slack User Group" attribute. In this example I've set it to "Incident Responders".

Save that entry, and you'll see that the members attribute for the team is now populated.

Those team members are the users that are in the Slack User Group "Incident Responders". We sync this data regularly, so if that groups changes in Slack, the changes will be reflected in the catalog.

You can now follow the instructions in Setting up Teams in Catalog to link the User type to the Team type to unlock the ability to filter incidents by team, and explore insights by team.

Did this answer your question?