SearchUnify supports permissions for the following content sources:
Salesforce
SearchUnify supports the following content permissions for Salesforce content repositories:
Object Level Permissions: All "object level read" permissions are supported through Salesforce profiles, which means if User A has Profile A and this profile does not have read access on case object then cases will not be displayed in search results to this user.
View All Data Permission: If a user has "view all" data permission, SearchUnify will show all results from all of the crawled objects to this user.
Channel Level Access to Knowledge Base: Access to Salesforce articles is controlled via channel information like public, customer, partner, or internal. SearchUnify respects the channel level information on Salesforce Knowledge and displays the results accordingly.
Community Sharing Settings: Access to objects like "cases" is controlled by sharing settings on communities in Salesforce. SearchUnify will support these sharing settings and will display results on the basis of these settings.
Category Permissions: Category visibility assigned to the user profile is useful while handling knowledge base permissions.
Khoros
SearchUnify supports the following content permissions for Khoros content repositories:
Board Level Access: SearchUnify shows results to users if the parent board is accessible to the user in the Khoros community.
In case of public search or search on any other platform, it would show data based on open boards.
Please Note: The permission of Khoros content is only supported when SearcUnify clients are used inside Khoros.
Zendesk
Tickets Level Permissions: SearchUnify supports ticket-level content permissions from Zendesk pages.
Jive
Security Groups and Roles Permissions: Security groups and roles can be fetched on the basis of user email and can be available on the document level.
Jira
Project Level Permissions: Project level permission implies the accessibility of the project that hosts the content (Issues, Tasks, Bugs) and is supported by SearchUnify
Issue Level Permissions: Not supported yet.
Confluence
Space Level Permissions: Space level permission implies the accessibility of the space which hosts the content (Pages) and is supported.
Page Level Permissions: In Confluence, permissions can be defined on page level as well. It has an interesting implication. If a user creates a page and changes the page level sharing setting to be visible only to them, then this page cannot be accessed by any other user even though they have access to the parent Space. SearchUnify handles this case well and provides support for such permission definition.
Google Drive
Own Content: Content created by the user itself is supported by SearchUnify.
Shared Content: All content that is shared with the user's email is also supported by SearchUnify.
Please Note: SearchUnify maintains a list of users who have access to respective documents and respects these permissions when a user performs a search.
HigherLogic
Community Level Permissions: SearchUnify supports community-level content permissions from HigherLogic.
Box
Own Content: This is the content created by the user itself and is supported by SearchUnify.
Shared Content: All content that is shared with the user's email is also supported by SearchUnify.
Please Note: SearchUnify maintains a list of users who have access to respective documents and respects these permissions when any user searches.
Dropbox
Own content: This is the content created by the user itself and is supported by SearchUnify.
Shared Content: All content that is shared with the user's email is also supported by SearchUnify.
User Permission: Not supported
Docebo
User Permission: SearchUnify support Courses level content permissions of the user.
Not Supported
As of now, permissions for the following content sources are not supported by SearchUnify:
- MindTouch
- MS Dynamics
- Slack
- SkillJar
- SharePoint
- ServiceNow
- Marketo
- Moodle
- Litmos
- HelpScout
- SABA
Comments
0 comments
Please sign in to leave a comment.