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 is only the activity data, and this type of sync happens only once at the initial stage.

2. Partial Sync: This sync takes place once every 24 hours; it fetches a list of licenses and users and replaces the list fetched from the previous sync.

So when a new instance of a new integration is connected, the user data doesn’t instantly show up in the modules. This information about sync time is conveyed to the user right next to the instance connection page through the "last sync time".

One integration can be connected multiple times with the same Zluri account by an organisation with different levels of scope and permission in Zluri. The user data for these instances are fetched separately. So, this feature is handy for organisations having subsidiaries using the same app or different departments using different accounts for an app.

The primary source for collecting Employee email id and other employee data, known as attributes, on Zluri can be selected manually by an organisation. In general, data is collected from all possible sources. The attribute fetched from the primary source overrides the same attribute fetched from other integrations. This applies to all integrations, irrespective of whether they may be an HRMS, SSO or other SaaS app.

So, to read employee attributes like Email ID, Departments etc., from a particular source, let’s say an HRMS, you will need to set the primary source for fetching the attribute to the app you want.

For instance-  

Suppose you have selected the Primary source for the Email IDs of employees on Zluri as Bamboo HR. Then, in the “Users” section on Zluri,  the Email IDs for the employees will be fetched from BambooHR and will not consider Email IDs fetched from other sources. 
But, 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.

It depends on the size of the organisation, as the size of data will generally depend on the organization's size. So fetching a large amount of data takes more time due to API rate limits for fetching data. Then, just fetching the data from API calls wouldn’t reflect it on the modules. The data is fetched in JSON format, which is stored in AWS S3, our cloud storage platform. The data for any organization can be found in S3 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 team and the data team then read and processed this data and stored it in DB. For every instance connected, we have a sync run time, which runs simultaneously every day (i.e. once in 24 hours).

Zluri asks for permission to collect data through integration; these permissions can be found under "Scopes" when connecting an integration.

Integrations are of two types, O-Auth Based and Form-Based.

Oauth integrations can be connected directly by logging in using the account for the application, and the scopes selected in Zluri will be listed as "Permissions requested by Zluri", and you will be required to accept these permissions to connect the application to Zluri.

Form-based integrations generally require you to generate API keys with Scopes you select on Zluri on the application, and entering this API key in Zluri permits Zluri to access data using this API key.

Scopes are also of two types :

"Required scopes" are the permissions required by Zluri to connect the integration; you can find what permission a scope is asking for and how it is utilized in the scope description.

"Other Scopes' ' are the permissions you can grant to Zluri to make use of other capabilities offered by Zluri, like Workflows and provisioning.

Zluri gets a lot of necessary User data when connecting through an SSO, for which you have to permit to use the required scopes.

Based on the SSO data, Zluri can identify applications used extensively by users within the organization. Zluri fetches the user data from the SSO application, which includes other User metadata like the Apps used by a user. Based on this data, Zluri detects the most used applications used by users across the organization. 

Zluri recommends these applications for integration since, given the large user base, getting information directly from these applications would ensure that only accurate data is populated on Zluri. Using Zluri for different capabilities for this integration is recommended.

You can find the Recommended integrations for your organization under : 
Sources - > Integrations -> Recommended

To sort integration based on user count, Go to integrations and choose recommended, click on sort by and select user count.

When an application integration approval is sent to a coworker, it must be actioned within 48 hours. After that, the link will expire. To view the link sent, you must go to Sources, then integration, and choose “ Connection Requests”.