Building Catalog items in Global vs. Scope

[zynsn]

Hi Developers,

What is the general consensus on building Catalog items in Global vs. Scope app? I've read some posts in the community where one would lean toward building catalog items in scope if it was intended for delegated development/citizen development. That is the only good reason I've come across so far while reading the posts in the community. What are everyone else's thoughts on catalog items in global vs. scope?

[Riya Verma · Accepted solution]

Hi @zynsn ,

Hope you are doing great.

There is no hard and fast rule dictating the placement of catalog items. It ultimately depends on the organization's needs, the complexity of the catalog items.

There are some pointers to decide whether to build catalog items in Global or Scope app:

1. If the catalog item is intended to be reused across multiple applications, it might be more appropriate to build it in the Global scope.

2.  In certain cases, it may be necessary to restrict access to catalog items based on application-specific roles and permissions --> such item should be preferred to be buitt in application scope

3.  Catalog items built within a specific application scope might be easier to maintain and upgrade, as they are tightly integrated with the application and its lifecycle.

4.  If your organization follows a centralized development approach, where a dedicated team handles catalog item development, building them in the Global scope can provide better visibility and consistency.