Zive enforces all access-level permissions of your source systems and business apps. That means users can only see things on Zive that they can see in the according source systems.
Where does Zive get the permissions?
Zive gets the applicable permissions from the according source systems. Today, most business apps offer specific APIs to fetch permissions or they deliver the applicable permissions as part of the data fetching APIs.
In the rare case that a source system doesn't provide access permissions through its APIs, the permissions will be defined globally at the level of the Zive data connector. In these cases the content from that source is typically marked as "internal public", meaning all employees will see the results in Zive.
How does Zive apply the permissions?
When Zive receives permission information from source systems they will be normalized to a group-based and user-based access control list (ACL) format. This allows Zive to enforce permissions across all data sources when users submit search queries or prompts to Zive. As a result, Zive's results and answers will only include information from sources that the current user has permission to access in the according source system.