---
schema_version: "1"
id: cee612b64945fa473fd616276275e5ae14b56c392f2b556d4b21d285e3575158
title: Packaging ConnectApi Classes
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/apexcode/apex_connect_api_packaging.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_connect_api_packaging.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: dcde8023ef4f61e67b162e208c87c5343853301c8df20c43502da7e5641d98a7
description: If you include ConnectApi classes in a package, be aware of Chatter dependencies.
---
# Packaging ConnectApi Classes

If you include ConnectApi classes in a package, be aware of Chatter dependencies.

If a ConnectApi class has a dependency on Chatter, the code can be compiled and installed in orgs that don’t have Chatter enabled. However, if Chatter isn’t enabled, the code throws an error at run time.

System.NoAccessException: Insufficient Privileges: This feature is not currently enabled for this user.

In its reference documentation, every ConnectApi method indicates whether or not it supports Chatter.

#### See Also

- [Develop and Distribute Apex for Managed Packages](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_manpkgs_chapter.htm "As an independent software vendor (ISV) or Salesforce partner, you can distribute Apex code to customer orgs by using managed packages. For first-generation managed packages (1GP) and migrated second-generation managed packages (2GP), use versioning to evolve components of your managed package gracefully without breaking existing customer integrations. Understand how global Apex in managed packages behaves and learn how to develop global Apex in managed packages specifically for agents.")