Before getting started, you'll need to choose the best type of environment for your team. This is an important step, as it will determine your team's functionalities, and this configuration cannot be changed later. However, you can rest assured that it is also possible to create new teams and remove old ones. Now, let’s explore the different team environments and how they will influence your use of the Deck data toolbox.
What is a Team?
First, let's define what a Team is within the Deck data toolbox and how it can be tailored for specific use cases. 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.
Choose a team configuration When you first create an account you will be asked to choose your default team environment.
Developer Environment: Technical, AVG 15-40 hours of work, Seamless Experience, API Data Exchange Automation
Ideal for companies looking to integrate Deck within existing websites, platforms, apps, onboarding flows, and data systems. This environment requires comprehensive technical knowledge and dedicated resources. The increased investment is rewarded by the following benefits:
Embed Link Widget for a more seamless user connectivity experience directly into applications, platforms, and user flows. End-users never have to leave your platform. Go full API Link Integration to end-user accounts to gain more flexibility in customizing unique user workflows and managing issues like errors or downgraded sources. Use API endpoints to retrieve JSON data and file formats from successfully connected sources. Data can be accessed once, or refreshed over time with a refresh API call. Within the developer environment, your team can access a Link editor, API keys, a sandbox, product selection, and a coverage page (coming soon).
No-Code Environment: No Dev Required, Instant Set-up, Source Management, Email Notifications, Connection Page, Self-Serve Data Tables, CSV, PDF, File Export
Ideal for companies looking to get up and running quickly without any technical resources. This environment has been built to support key workflows for our main products with a self-serve customer experience but offers less flexibility around unique edge cases.
Easy configuration and team collaboration with sets of pre-built permissions, notifications, and management rules. Send out new source connection requests to internal or external end-users and manage connected sources over time. Assign those sources to individuals (Identity, Credit Risk, Payments) or sites (Sustainability, Accounting). End-users can connect to sources directly on a self-hosted landing page tailored to your branding. Internal collaborators can view data using an intuitive dashboard and export outputs in CSV or PDF formats.
Choose your No-Code environment main object If your preferred option is the no-code route, you’ll then need to determine the main object for this environment. This is an important step as it will define how your connected sources are structured around a specific object and how we will group your data endpoint. Here’s your two options:
By Site Ideal for Sustainability, Accounting, Bills, and Energy Management:
A site-based object is often the preferred option for companies using decks to streamline business accounts for Sustainability, Accounting, or Bill Payments use cases. By selecting this object, your source management will be centered around sites and their metadata. You will have a dedicated section for adding and managing sites. Additionally, you should appoint site managers responsible for the sources at assigned sites, either by connecting themselves or delegating the connection to someone else. Data outputs will be aggregated in the same data table for all connected sources within the same team, and you will be able to filter this data table using various properties (like site, country, etc.).
By Individual Ideal for Fintechs, Payments, and Account Switching:
An individual-based object is often the preferred option for fintechs using decks to retrieve accounts from individuals (and/or businesses) for specific purposes such as loan approval or digital onboarding (IDV). By choosing this object, you will have a streamlined process to create new requests and notify end-users to connect one or multiple accounts. These end-users are notified by the system and can access a branded, self-hosted landing page to connect accounts. Data outputs will be centered around specific individuals with an intuitive dashboard, allowing internal collaborators to manage open requests.
It’s all about the journey We all start our journeys with a specific desired outcome, but how we get there can look different from one company to another. The deck team wanted to package as many options into our data toolbox in a way where you can easily start using our data and can build more comprehensive experiences or automation over time.
Like any project, every business should take into consideration their available resources, timelines, customer expectations, and end goals to define how they can best get there. Our team is here to support you through this journey, so don’t hesitate to reach out.