Apigee Teams Feature Requirements

Background & Business Value

Currently applications are associated with the user that creates them. At the moment, we have asked all users to create Functional Accounts in order for Teams to have a shared username/password combination that they can use as a group to access their departments applications. We need a better way to associate an application with a Team or a group of people.

Apigee provides this functionality in a "Companies" feature that is part of the Enterprise package. We can use the Companies feature on the portal without paying for the Enterprise package. However, we will need to implement the UI for working with the underlying technology ourselves.

Goals

• Add the ability for Teams to Manage Applications.
• Remove functional accounts.
• Allow the API Consumers to Create and Manage their own Teams.
• Develop slack commands to provide Apigee Admins the ability to Manage Teams.

Assumptions

• Will use apigee_nonmint_company feature.

Out of Scope

• Asking Campus IdM to create "Team Accounts"
  • Alternatively to implement the Apigee Companies feature we could ask campus to create "Team Accounts" in the Campus IdM. But, it really seems like a bad idea compared to Apigee's Teams Feature.

Project Timeline

Requirements Documents

Add New Requirements