Note: This is a work in progress page as we're constantly updating our services.

Developer Profile:

1. Developers have restricted access; they can only edit applications created by the super admin and cannot create new apps. They also can't export applications.
   
2. Developers can only publish apps to the Stage environment if granted permission by the super admin. 
   
3. They are not permitted to submit apps to the Zoho Marketplace.
   
4. Developers cannot add new clients when privately distributing apps. Their role is limited to sending updates to clients.

Feature Limitations:

1. Custom AI models cannot be created, limiting AI-driven solutions within the app.
   
2. The use of Augmented Reality (AR) fields is restricted.
3. Under Microservices tab only connections are supported.
4. Custom connectors are not supported. Only built-in connectors are supported.
5. Payment connectors under built-in connectors are not supported.
6. System integrations and payment workflows are not supported.
7. Custom APIs cannot be created.
   
8. Integration forms and fields are not supported.
   
9. Pivot charts and tables are not supported, limiting advanced data visualization options.
   
10. Uploading and using account-level images for custom elements in pages is not supported.
    
11. Configuring payment workflows is restricted, preventing the setup of payment transactions within apps.
    
12. Cloud functions (java and node.js) are unavailable for executing custom code.
    
13. The 'From' address in send mail workflows cannot be hardcoded or contain a verified email address.
    
14. Configuring user fields in components is restricted, limiting flexibility in user-based interactions.
    
15. App variables cannot be created, reducing dynamic customization options.
    
16. Custom notifications within the app are restricted, limiting in-app communication options.
    
17. Cross-app referencing is restricted, limiting integration with other applications.
    
18. The creation of portals is restricted.
    
19. Publishing individual components, such as forms, reports, and pages, is not supported.
    
20. Backup options for apps are limited, restricting data and application recovery.
    
21. The date and time formats in installed applications cannot be changed.

Application Development Restrictions:

1. For a Marketplace application, editing the app name and app logo is allowed only until the app is published to the Marketplace.
   
2. For a private application, editing the app name and app logo is allowed only until the app is published to the first client.

Publish to Stage:

1. When a developer tries to publish the changes from the Development environment to the Stage environment, they cannot select more than 500 component changes in a single publish.
   
2. If a version is submitted to the Marketplace, further publishing to the Stage environment is not allowed until the review process is complete i.e., publishing an app to Stage with the status 'Under Review' is not possible.

Marketplace submission Limitations:

1. The total component changes made to an application that can be sent as an update can't exceed 1,000. For example, an application version v5.0 is published to Marketplace as release version 1.0. Then the developer submits application version v10.0 as the next submission to Marketplace. Here, the sum of all component changes from  application version v5.0 to v10.0 can't exceed 1,000.
   
2. Only five release versions of an app can be active at any given time when distributing through Marketplace. Once a new version is submitted and approved, the oldest version will be deprecated. Users on a deprecated version will need to update their application to a supported version within 120 days to avoid the app being disabled. For example, if release versions R1 to R5 are active and R6 is submitted for review, R1 will be deprecated upon R6's successful review. Clients or users who are on release version R1 will need to update their application to the next version.

Private distribution Limitations:

1. Only versions higher than the last update sent can be sent as updates to clients. For example, if a client is using version 3.0 and version 5.0 is sent as an update but not installed, and the app has since reached version 10.0, you can only send versions higher than 5.0 as further updates.
   
2. Only the most recent 30 versions of a private app remain active. Older versions are automatically deprecated by the system. If a client is using a deprecated version, for a developer publishing changes to the stage environment, it will only be allowed after a mandatory update is sent to the clients. Clients must install this mandatory update within 30 days.
   
3. Once a mandatory update is sent, no further updates can be sent until the client installs the mandatory update or the mandatory update itself becomes deprecated.