What is a limitation of an API token with custom scope in the Celigo platform?

What is a limitation of an API token with custom scope in the Celigo platform?

• A. Cannot perform CRUD operations
• B. Can only read existing records
• C. Can only create new records
• D. Cannot access exports

Answer: (A)

An API token with a custom scope in the Celigo platform does have certain limitations that restrict its functionality. Specifically, it cannot perform CRUD (Create, Read, Update, Delete) operations across the board. This limitation arises from the fact that a custom scope is designed to provide a more granular level of access, allowing users to tailor the permissions for their integrations. If the token's scope is limited, it may exclude certain operations altogether, thus preventing the full range of actions that an API token with broader access might allow. By indicating that it cannot perform CRUD operations, the correct answer highlights a crucial aspect of API token management, which focuses on the permissions associated with various actions within the platform. In contrast, the other choices suggest operations that are either fully constrained or represent an incomplete picture of what can be accomplished with a custom scope. The detail in option A effectively captures the essence of the limitations imposed on the token's capabilities when a custom scope is defined.

An API token with a custom scope in the Celigo platform does have certain limitations that restrict its functionality. Specifically, it cannot perform CRUD (Create, Read, Update, Delete) operations across the board. This limitation arises from the fact that a custom scope is designed to provide a more granular level of access, allowing users to tailor the permissions for their integrations. If the token's scope is limited, it may exclude certain operations altogether, thus preventing the full range of actions that an API token with broader access might allow.

By indicating that it cannot perform CRUD operations, the correct answer highlights a crucial aspect of API token management, which focuses on the permissions associated with various actions within the platform. In contrast, the other choices suggest operations that are either fully constrained or represent an incomplete picture of what can be accomplished with a custom scope. The detail in option A effectively captures the essence of the limitations imposed on the token's capabilities when a custom scope is defined.