║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║

---

title: Features description: Grant access to your privileged content and data using features.

Features are specific capabilities or functionalities in your application that you want to control access to. They are used in authorization checks.

Features can be used in two ways:

• With Clerk's organizations feature to create custom permissions. Custom permissions are always tied to a feature, and are formatted as org:<feature>:<permission>. For example, you could create a feature called invoices and then create a new permission called create invoices. The custom permission's key would be org:invoices:create. Learn more about custom permissions.
• With Clerk's billing feature to create features specific to a subscription plan. See the billing docs for more information.

To manage your features, navigate to the Features page in the Clerk Dashboard.

║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║