Updated on by Susanna Fagerholm
Effective Account Management in Cyclr is a key element of building scalable integrations. A well-organized account hierarchy isolates data, offers clear oversight of customer usage, and supports scalability as the platform grows.
One of Cyclr’s many selling points is its customizability, and that applies to account structuring as well. Cyclr supports multiple approaches to structuring accounts, depending on the use case. So let’s take a deep dive into Cyclr’s accounts and users, and discuss the recommended practices for organizing them.
Accounts and Users – Overview of Cyclr Account Structure
First things first, let’s get the obvious out of the way: what are Accounts and Users in Cyclr, and how do they differ?
In Cyclr, the Partner Console serves as the central hub for managing integrations. Two key components of this structure are Accounts and Users.
Accounts are areas within the Partner Console that hold integrations for individual customers. They function as isolated containers for each customer’s connectors, integrations, and authentication details, while remaining invisible to end-users. Typically, there is a one-to-one relationship between a Cyclr Account and a customer account in the partner’s own application or platform.
Users, on the other hand, provide controlled access to Accounts and Sub Accounts. Users can have varying permission levels on different Accounts to perform actions such as creating cycles or authenticating connectors.
In a nutshell, each customer should have their own Account, and those Accounts can be authenticated and accessed via Users.
The Role of Accounts
Each Cyclr Account serves as a dedicated space for managing one customer’s integrations. This multitenant design keeps customer data isolated and secure, preventing any risk of cross-contamination between accounts. At the same time, Accounts also give SaaS companies better visibility into how their customers use the platform, including the connectors and cycles they access most frequently.
Through Accounts, integrations can be tailored to specific customer needs. Connectors can be installed, template integrations deployed, and custom cycles built to support unique requirements. Additionally, Accounts can leverage features such as Marketplaces to let customers deploy templates independently while maintaining isolation from other accounts.
Best Practices for Account Management in Cyclr
Account management in Cyclr vary a lot depending on each company’s specific use case. However, as mentioned previously, the best general practice is to assign one Account per customer. This ensures a clean separation of data and simplifies the monitoring of individual customer activity.
Companies can organize multiple related accounts further with Sub Accounts. These sit under Accounts in the account structure, inheriting all the installed connectors from the parent account.
Sub Accounts
Sub Accounts simplify account management by inheriting connectors from their parent Account, which eliminates the need to configure the same connectors repeatedly. Despite sharing connectors, each Sub Account maintains its own concurrent transaction limits and can host its own exclusive Cycles.
A single Account can have multiple Sub Accounts. For example, a franchised business use a parent Account for the main franchise, and provide each branch their own Sub Accounts. This way the customer can easily employ the same general integrations across their franchise, while allowing each branch to customize its own cycles where needed.
Users
Users, sometimes also known as Account Users, provide controlled access to Accounts and Sub Accounts. A single user can be given access to one or more Accounts and Sub Accounts.
Businesses can assign their users admin rights for full account management, including settings and user invitations, or limited access to utilize existing connectors and create cycles without administrative privileges.
SaaS companies that want to maintain complete internal control can also create Users programmatically through the Cyclr API. Customers can still authenticate connectors via an emailed authentication link, without ever accessing Cyclr directly.
Console Users
It’s very important not to confuse Account Users with Console Users.
Console Users are internal team members that have access to the Partner Console to manage templates, Accounts, and reporting. This access is intended solely for the SaaS business and must never be granted to customers or end-users.
Console Users can be added or managed under Settings in the Partner Console.
Conclusion
Cyclr’s flexible embedded integration platform provides the foundation for organized, scalable, and secure account management. Assigning dedicated Accounts for each customer, leveraging Sub Accounts for related entities, and carefully managing Users ensures that customer data remains isolated while supporting operational efficiency.
A well-structured account hierarchy offers businesses a flexible way to manage their customers’ integrations and organize them neatly and securely. This allows businesses to ensure that their customers’ data remains isolated and protected, without having to compromise on their product’s scalability.
