FAQ

How long does it take for a newly connected integration’s data to be fetched? What are data syncs and its types?

Data syncs are of two types:

1. Full Sync: This type fetches last year’s data from SSOs like Google Workspace or Azure AD. This includes only activity data and happens only once during the initial setup.
2. Partial Sync: This sync occurs once every 24 hours and fetches a list of licenses and users, replacing the list fetched from the previous sync.

When a new integration is connected, user data doesn’t instantly show up in the modules. The sync time information is displayed to the user next to the instance connection page through the "last sync time".

What is "connecting multiple instances of SaaS applications"? Are the number of direct integrations for competitors the same, or do they need to be updated?

One integration can be connected multiple times to the same Zluri account by an organization with different scopes and permission levels. The user data for these instances is fetched separately. This feature is useful for organizations with subsidiaries using the same app or different departments using separate accounts for an app.

While onboarding a user, does Zluri read their data (such as email ID, etc.) from an HRMS system?

The primary source for collecting employee email IDs and other employee data (known as attributes) on Zluri can be manually selected by an organization. In general, data is collected from all possible sources, with the attribute fetched from the primary source overriding the same attribute fetched from other integrations. This applies to all integrations, whether they are HRMS, SSO, or other SaaS apps.

To read employee attributes like email ID and departments from a particular source (e.g., an HRMS), you need to set the primary source for fetching the attribute to the app you want.
For instance:
If you have selected Bamboo HR as the primary source for employee email IDs, then in the "Users" section on Zluri, the email IDs for the employees will be fetched from BambooHR and not from other sources. However, if a user found on Zluri through one of the integrations is not present on Bamboo HR but is relevant to the organization, then the email ID for that user will be fetched through that integration.

I want to connect to 2-3 integrations. How long does it take to display the data from these new integrations?

The time depends on the size of the organization, as the data volume generally correlates with the organization's size. Fetching large amounts of data takes longer due to API rate limits. After data is fetched via API calls, it is stored in JSON format in AWS S3 (our cloud storage platform) under:

Zluri integrations -> *Org ID* -> *Integration ID* -> *Instance ID* -> *Year* -> *Month* -> *Date* -> *Sync ID*

All files and data obtained from that application are stored there. Once the sync is finished, processing starts. The integration and data teams read and process the data, storing it in the database. For each connected instance, there is a sync runtime, which runs daily (i.e., once every 24 hours).

How do Zluri notifications on Integration Connection Requests work?

When an integration is connected via the invite flow, i.e. when you Send the integration connection request to a coworker, all the future notifications regarding the integration will go to the one who connected the integration. 

In cases when an integration becomes erroneous and is connected via invite, Zluri triggers a notification in specific intervals(2,7,15.30 days) to the user who connected the integration in the first place to reconnect the integration. 

The user needs to approve the reconnection request, in case, the user decides not to connect the integration again, Zluri will keep on notifying the user to reconnect the integration in the intervals(2,7,15.30 days) mentioned.