Understanding the different account types and roles on the Crossing Minds API is crucial for managing access and permissions effectively. This guide will help you differentiate between individual and service accounts, as well as the various roles and their associated permissions.

Account Types

Navigating the Crossing Minds API requires a solid understanding of the two main account types: individual and service accounts. This section explores the differences between these account types, their purposes, and their unique characteristics. By learning how to distinguish between individual and service accounts, you'll be able to manage access and resources effectively, ensuring a smooth and secure experience for your team and your ecommerce or B2C business.

Individual Accounts

Individual accounts are intended for real persons and are identified by an email address. The email must be verified so that reset password emails can be sent securely. These accounts are suitable for developers, content managers, and other team members who require access to the platform.

Service Accounts

Service accounts are designed for backend or frontend scripts and are identified by a service name. They are simpler to create, as no email validation is required. However, reset password emails cannot be sent. Service accounts are ideal for automated processes, such as data import or export tasks.

Roles

Effectively managing roles and permissions on the Crossing Minds API is essential to maintain a secure and well-organized platform. This section delves into the four main roles available: root, manager, backend, and frontend. Each role comes with specific permissions, allowing you to control access to various resources and functionalities. By understanding the nuances of each role, you can tailor access for team members and automated processes, ultimately enhancing the performance and security of your ecommerce or B2C business.

Root

The root role has full permissions and is automatically assigned to the root account of your organization. This unique "system role" can access all features and manage all resources.

Manager

The main difference between the manager and root roles on the Crossing Minds API lies in their scope of permissions. The root role has full permissions, granting access to all features and resources, and is automatically assigned to the root account of your organization. On the other hand, the manager role also has full permissions but is assigned on a per-account basis, allowing users with this role to manage accounts, databases, and other resources within their assigned account.

In other words, while the root role is ideal for a single, all-encompassing user, the manager role is suitable for assigning specific permissions and access to individual accounts. For businesses with multiple accounts and users, the manager role is the preferred option for effective management of resources and access.

‍

Backend

The backend role has full permissions for endpoints under the "database" resource. Users with this role can manage databases and their contents but cannot create or delete accounts or databases.

Frontend

The frontend role is used to limit permissions to read and write on resources belonging to a specific user of your app and getting recommendations for this specific user. Specifying the user is done during login and not during account creation, meaning you don't have to create one account with the frontend role for each user. This role is ideal for managing user-specific data and ensuring personalized recommendations.

‍

When to use Backend VS Frontend service accounts

The backend and frontend roles on the Crossing Minds API offer specific permissions and limitations for accessing and managing resources. The backend role grants full permissions to endpoints under the "database" resource, allowing users to manage databases and their contents. However, users with this role cannot create or delete accounts or databases.

The frontend role is designed to limit permissions to only read and write on resources belonging to a specific user of your app, and getting recommendations for this specific user. Users can specify the user during login, allowing for personalized recommendations and data management. Unlike the backend role, the frontend role cannot create or delete databases or accounts.

The main difference between these two roles lies in their scope of permissions and their intended use. The backend role is suitable for managing databases and their contents, while the frontend role is designed for managing user-specific data and ensuring personalized recommendations. By understanding the limitations and differences between these roles, businesses can tailor access and permissions effectively, ultimately enhancing the performance and security of their ecommerce or B2C business.

‍

‍

‍

‍

‍

‍