Send Docs Feedback

Note: Most user interface tasks can be performed in Edge Classic or the New Edge experience. For an overview, getting started topics, and release notes specific to the New Edge experience, see the docs.

Managing role-based access to content on your developer portal

When creating content on your Apigee Developer Portal, you may want to control the content that is displayed based on user role. For example, you may want to limit access to an API to Beta participants only. You'll need to remove any access limitations to the API once it is officially released.

You can manage role-based access to content on your developer portal using the following Drupal modules:

  • Content Access - Manage access to content types by role or author. The developer portal is packaged with the Content Access module, though it is disabled by default. There are pros and cons to using the content access modules, as described in Content Access Control on Dev Portal. This article provides links to more information about using each module.
  • Taxonomy Access Control - Manage access to specific nodes (or pages) rather than an entire content type. The developer portal is not packaged with the Taxonomy Access Control module by default; you will need to download and install it. For steps to add role-based access to the SmartDocs content on your developer portal using the Taxonomy Access Control module, see Content Access Control on Developer Portal SmartDocs Documentation.
  • DevConnect Limit API Product By Role - Manage access to API products by role. The developer portal is packaged with the DevConnect Limit API Product by Role module, though it is disabled by default.

    Video: To learn about how to use the DevConnect Limit API Product by Role module to manage access to API products by role, watch the following video.

 

Help or comments?