Selecting the Object

Next, you’ll be asked 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 Deck 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 can appoint site managers, responsible for the sources at assigned sites. Site managers can either make the connection themselves or delegate the connection to someone else. Data output 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 Request

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.

Important Considerations for Team Configuration

It's crucial to note that once a team is created, its main configuration cannot be changed. However, you will always have the flexibility to create a new team within your company account with a different configuration. This feature is particularly beneficial if you plan to transition from a no-code environment to an API integration with third-party platforms, such as Carbon Accounting Software.