Open Community Access
Open Community Access
Open Community Access (OCA) provides read-only access to the entire repository in Prolaborate. Users can access repository information on live with a short URL link which does not require any authentication.
Prerequisites
Open Community Access should be purchased as an ‘Add-on’ to be included in the Prolaborate License
Admin should have access to the repository to enable the option in Repository Settings
Note:
This feature is only available from Prolaborate version 4.3
Due to security reasons, OCA is available for an ‘On Premise’ environment
It is free for Large Teams and Enterprise editions of Prolaborate. For the Growing Teams edition, the feature must be purchased as an add-on
For a Cloud environment, the customers must purchase a Read-Only license additionally to obtain the same benefit
Enable Open Community Access
To enable Open Community Access, go to Menu > Repository Settings. Toggle the button under Open Community Access to enable the feature. Once enabled, click Save to save the configurations.
1-enable-open-community-access
Share a Repository
After enabling Open Community Access and saving the configurations, navigate to the ‘Repositories’ listing page. Share option will be enabled under Actions column for each repository.
2-share-repository
Click on it to open Share Repository popup window where a short URL will be available with the alias name given to the repository.
Click Copy icon to copy the URL. Once copied, simply share the URL with your users to give them read-only access to the entire repository.
3-copy-url
When users visit the URL provided, they see default dashboard set for the repository and the contents in Repository Browser, based on the Sections configured for the specific repository.
Open Community Access
Open Community Access (OCA) provides read-only access to the entire repository in Prolaborate. Users can access repository information on live with a short URL link which does not require any authentication.
Prerequisites
Open Community Access should be purchased as an ‘Add-on’ to be included in the Prolaborate License
Admin should have access to the repository to enable the option in Repository Settings
Note:
This feature is only available from Prolaborate version 4.3
Due to security reasons, OCA is available for an ‘On Premise’ environment
It is free for Large Teams and Enterprise editions of Prolaborate. For the Growing Teams edition, the feature must be purchased as an add-on
For a Cloud environment, the customers must purchase a Read-Only license additionally to obtain the same benefit
Enable Open Community Access
To enable Open Community Access, go to Menu > Repository Settings. Toggle the button under Open Community Access to enable the feature. Once enabled, click Save to save the configurations.
1-enable-open-community-access
Share a Repository
After enabling Open Community Access and saving the configurations, navigate to the ‘Repositories’ listing page. Share option will be enabled under Actions column for each repository.
2-share-repository
Click on it to open Share Repository popup window where a short URL will be available with the alias name given to the repository.
Click Copy icon to copy the URL. Once copied, simply share the URL with your users to give them read-only access to the entire repository.
3-copy-url
When users visit the URL provided, they see default dashboard set for the repository and the contents in Repository Browser, based on the Sections configured for the specific repository.
4-view-repository
Revoke OCA Share
Users are allowed to revoke share for the shared repository by disabling Open Community Access. To disable, go to Menu > Repository Settings. Toggle the button under Open Community Access to disable the feature. Once disabled, click Save to save the configurations.
After disabling the feature, the previously shared URL becomes invalid.
Note:
After enabling Open Community Access, the Private Share URLs will work as a Public Share where read-only access is given to the entire repository
Only default dashboard set for the repository will be displayed to the users while accessing the repository using via ‘Open Community Access’
Users can view the discussions but cannot participate in one
Users cannot access Reviews
4-view-repository
Revoke OCA Share
Users are allowed to revoke share for the shared repository by disabling Open Community Access. To disable, go to Menu > Repository Settings. Toggle the button under Open Community Access to disable the feature. Once disabled, click Save to save the configurations.
After disabling the feature, the previously shared URL becomes invalid.
Note:
After enabling Open Community Access, the Private Share URLs will work as a Public Share where read-only access is given to the entire repository
Only default dashboard set for the repository will be displayed to the users while accessing the repository using via ‘Open Community Access’
Users can view the discussions but cannot participate in one
Users cannot access Reviews
Related Articles
Troubleshooting - Sections and Access Permissions
Q1. Unable to access elements in a diagram located in a different package Description The customer was unable to access elements in a diagram that are located in a different package. Troubleshooting steps The error message "No access to the Artifact" ...FAQs - JIRA
Q1. Links generated from Jira Items are exposing the entire repository when accessed Answer This behaviour is intentional, as Jira provides only essential information, and users typically access Prolaborate to access comprehensive data. If you wish ...FAQ's - Sections and Access Permissions
Q1: Can Prolaborate update data e.g. Notes or Tagged value even if my EA permissions is set to read only? Answer EA and Prolaborate access permissions are different. The Prolaborate users have different access permissions. So, the users will be able ...Prolaborate Access Control & SSO
This document consolidates information from customer reported issues and FAQs related to Prolaborate’s Access Control Profiles, SAML Single SignOn (SSO) configuration, readonly access, and a known login issue after license changes. It is intended to ...Known issues - Analyzer
Q1: Images exported from Analyzer are not clear if they have more number of nodes Description The images exported from Analyzer are not clear enough if they have more number of nodes. You should be able to find the difference in the images attached ...