Introduction to Teams

Over time, you will have the ability to add or remove teams.

At Deck, a team is a unique instance with its own set of link parameters, APIs, products, link configurations, and datasets. A company might choose to maintain only one team for simplicity or multiple teams to support a complex and diverse set of use cases within the organization.

There are several reasons you might need more than one team:

Customization Between Locations: If your operations span multiple regions, you may find it beneficial to create a separate team for each region. This allows you to customize your Link widget to support different source types, statuses, languages, and branding adjustments.
Handling Large Numbers of Sites or Requests: To manage a large number of sites (like those for Sustainability/Bill Payments) or requests (such as Identity, Credit Risk, Employment), you may want to distribute these across several teams to better manage connection volumes and data.
Language Support: If you need to support multiple languages, you should create a separate team for each language. This is necessary because your Link widget, branding, and landing pages can only support one language at a time.
Diverse User Experiences and Workflows: Companies often need to cater to different user flows, which may require unique source configurations. By creating a separate team for each workflow, you can ensure the exact configuration needed is in place.
Data Segregation: Keeping data segregated can be crucial for managing privacy, security, or regulatory compliance.
Running Different Environment Types: Some companies may need to implement different environment types for specific use cases or workflows. For example, embedding a Link widget and retrieving data via API for one workflow, and using a self-service dashboard for another to send links to end-users and view data.
Providing Distinct Experiences to Customers (for Partners): As a platform or consultant aiming to provide a turnkey experience to your clients, creating individual teams for each customer allows them to manage their connections and data in separate instances.

This framework ensures that your team's setup in the Deck data toolbox is optimally configured for your specific business needs and objectives. It’s important to note that your subscription and billing will encompass all of the underlying team's volume.