Onboarding Process

  • Onboarding Process

    The onboarding process of the Zluri comprises three steps:

    1. Add your organization details

    2. Connect SSO 

    3. Connect financial integration

  • Adding Your Organization Details

    To get started, you need to enter the following information -

    • Your organisation name

    • Default currency used 

    • Starting the month of your financial/fiscal year

  • Why enter Organisation details?

    Filling out these details is essential as we analyse and present all the spending in the default currency and for the current financial year. Zluri supports all global currencies (179 of them) on the platform. The default currency can be selected for the organisation while onboarding and the spend reports will be generated in the default currency. 

    Note: The transactions that don’t take place in the default currency will be reported after conversion and formatting.

  • Connecting Your SSO

    Zluri requires you to connect your SSO service provider to add your team to the app. It supports various SSO service providers such as Google Workspace (formerly GSuite), Azure AD, Okta, OneLogin, JumpCloud, etc. You can also add these details via a CSV file.

  • How to connect SSO?

    • Integration with any SSO requires authentication from the SSO account’s administrator.

      • For example, if you have the Google Workspace Admin credentials, you can authorize the integration yourself. Or you can invite Google Workspace Admin to complete the authorization with Google Workspace.

    • If you invite your co-worker (SSO admin) to complete the authorization, you'll need to fill in their name, email, and a note (optional), and we will invite them.

    • After the above step, your account admin will get an email with a link to complete the authorization and will see a screen as shown below after they complete the step.

    • Once the SSO is connected, you'll see a blue checkmark on the top right corner as shown in the below pic for Google Workspace.

  • Why should I connect the SSO?

    • Connecting the SSO is important as Zluri fetches the list of users, the applications they use, sign-in/sign-out activities, departments, domains etc., and the SSO is generally the primary source for most of the organisation’s data.

    • SSO is important for shadow IT discovery, Identifying employees vs external users, user status, departments, designations of employees, etc.

    • It also provides user activities for the applications which do not have a direct integration with Zluri. It helps Zluri calculate usage scores for each user for each application needed for optimisation insights.

  • Best practices

    If you have just one SSO instance, connect to that instance only once. If it is disconnected, do not add another instance and instead reconnect the existing instance.

  • Connecting Your Financial Integration

    After connecting with your SSO integration, you'll need to add the transactions through an integration with your financial systems like Quickbooks, Xero, etc.

    You can skip the “add transactions” step and be redirected to your dashboard to view the users, applications, and usage metrics. You can integrate the financial system later by visiting the integrations page or upload the transactions by visiting the upload transactions page.

  • How to connect Financial Integrations?

    1. Like SSO integration, financial integrations also require the account’s administrator authentication.

    2. For example, if you have the Quickbooks admin credentials, you can authorize it yourself or send an invite to your Quickbooks Admin to complete the authorization with Quickbooks.

    Once you follow all the steps and connect financial integration, Zluri will fetch the transaction data from your financial system and automatically map those transactions to the SaaS applications.

  • Best Practices

    • Please use the transaction type/account type filters to fetch only relevant transactions from the financial systems. If unsure, you can connect without applying filters and see the transaction data with transaction type and account type data in the platform. 

    • Zluri automatically maps transactions to SaaS applications by matching the transaction description with application names. In case it’s not able to map, you can map manually and select ‘Auto assign for all future transactions’ so that Zluri can save the pattern and map all transactions of similar patterns to the same application.

    • Always check the unrecognised section of the transactions tab. You can move those transactions either to the recognized tab if it's a SaaS-related transaction or to the archived tab if it's a non-SaaS-related transaction.

  • Initial Setup

    After the signup and onboarding processes, you must complete your account's initial setup. 

    To set up your account, navigate to Settings -> Your Organization within the Zluri app.

    • You can edit details such as Company name, Payment owner and IT owner in this tab.

    • Payment owners will be notified about any transaction-related activity. 

  • Trusted Domains

    Trusted domains contain the list of domains identified from various sources such as SSO. You should verify and ensure all the domains approved for use by your organisation are listed here. You can locate them within Settings -> Your Organization -> Trusted Domains

  • Why does Zluri need trusted domains?

    • Zluri utilises trusted domains to identify external users in your organisation, allowing you to manage them seamlessly.

    • Trusted domains are essential while setting up SAML. When you set up a SAML login for your organisation’s users to Zluri, only users from trusted domains can log in to Zluri. 

  • Best Practices:

    If the required trusted domains are not auto-detected, contact the designated Customer Success Manager for your account.

  • Integrations

    Now that you have completed the initial onboarding and set-up, it’s time to enrich Zluri with data from more direct integrations.

  • Connecting HRMS

    At this stage, you should have already connected your SSO and financial system to Zluri. The next application you should connect to Zluri is your HRMS. 

    Connecting your HRMS app with Zluri provides valuable user data like Department, Designation, Reporting Manager and Joining Date. Since Zluri can fetch accurate user Metadata from your HRMS integration, you can choose to configure your HRMS as your primary source for user data.

  • Recommended Integrations

    After connecting to your SSO, Financial System and HRMS, Next, you should take a look at the recommended integrations.

    Recommended integrations are the list of apps used by the users in your organisation which are discovered using the integration with your SSO. 

  • Why should I Integrate applications?

    Zluri suggests you connect as many integrations as possible as that gives Zluri more accurate information about users, licenses, and usage activities which helps Zluri provide better insights.

  • How do I connect Integrations?

    You can find the steps to connect a particular integration in the “How To” page of the application, or you can find the steps to connect while connecting directly by selecting the “+Connect” button. You can find detailed screenshots and steps for each app available for integration on Zluri.

    Steps to connect - 1. Integration details screen for Postman integration

    Steps to connect - 2. Connect instance screen for Postman integration

    There are two ways to connect an integration: You can either connect the integration yourself or send a connection request to a coworker. The co-worker will get a link to connect the integration on mail, which can be accessed without logging in to Zluri. Please ensure that the person has the necessary permissions for that app required for connecting a particular integration. 

  • Understanding The Scopes Requested

    Scopes are the necessary permissions required by Zluri for connecting an integration to Zluri. Different scopes provide different capabilities for you on Zluri, such as Discovery, workflow, Provisioning, and Audit logs.  

    • Scopes can have read or write permission. Scopes with read permission can fetch data on Zluri, and those with write permissions give Zluri access to read and edit the data. 

    • Scope sensitivity is a measure of the sensitivity of the data Zluri can fetch using the scope and the level of access it gives to Zluri.

    When connecting an integration, you'll see a list of scopes separated into two sections:

    1. Required scopes: Required scopes are the necessary permissions required by Zluri to connect an app with Zluri. So, these scopes are selected by default while connecting.

    2. Other scopes are the permissions required by Zluri if you need Zluri to provide you with all its capabilities, like workflows and provisioning. You’ll need to select these scopes while connecting an integration.

  • Understanding Integration Capabilities

    Each integration might have different capabilities based on the APIs available. You can visit the capabilities section of an integration to find out the data Zluri can fetch from the integration and the workflow actions available for that integration.

  • Best Practices

    Disconnected Integrations:

    A connected integration can be disconnected due to many reasons. The API key might have expired, the person who authorised the connection may have left the organisation, or their permission levels might have changed. 

    When an instance is disconnected, instead of connecting a new instance, you can reconnect the previously disconnected instance. You can use previously used credentials, for instance, and new credentials to reconnect the instance. So, the API call triggered for the same instance will completely update the old data associated with the instance with new data fetched, leaving no chance for stale data or any data discrepancies.

    Multiple instances:

    Zluri allows you to connect multiple instances of the same application. It should be used when you have multiple accounts of the same application. The same account should not be connected multiple times since it might result in data discrepancies.

  • FAQs

    How frequently does Zluri sync the data from the connected applications?

    After connecting an integration, it takes about 24 hours for a sync to fetch the user data and other metadata from the integration to reflect on Zluri’s platform. 

    What data does Zluri fetch from the integrations?

    The kind of data Zluri fetches from any integration varies from one integration to another. But primarily, all integrations can be segregated into four major categories.

    1. SSO: ZLuri fetches the list of users, their metadata, activities, domains, and applications from SSO.

    2. HRMS: HRMS integration is used to fetch user metadata like departments, designations, reporting manager, date of joining/leaving, etc.

    3. Financial Integration: Zluri fetches a list of transactions from financial integrations

    4. Other applications: Zluri fetches a list of users, licenses, activities etc., from other direct integrations like Slack, Zoom, etc.

    What do you do when you do not find an application in the integration catalogue you wish to connect with?

    If the application has open APIs, Zluri can build the integration. You can reach out to your designated Customer Success Manager for more details.

  • Primary sources:

    After doing the initial setup and checking trusted domains, you need to update primary sources for various details in the Zluri app. These details are - 

    • Department

    • Designation

    • Profile Image

    • Users

    • Reporting Manager

    • Joining Date


    1. Department - Department’s primary source is the app for fetching the departments, their users, and other department data in your organisation.

    2. Designation - Designation’s primary source is the app used for fetching designations for users in your organisation discovered/added on Zluri.

    3. Profile Image - The profile image’s primary source is the app used for fetching Profile images for the users in your organisation discovered or added on Zluri.

    4. Users - Users’ primary source is the app used by Zluri for fetching the list of all users present in your organisation.

    5. Reporting Manager - Reporting manager’s primary source is the app used for fetching Reporting managers for the users in your organisation discovered/added on Zluri. 

    6. Joining Date - Joining date’s primary source is the app used for fetching Joining dates for users in your organisation. 

  • Why update primary sources?

    1. Selecting primary sources is essential as they provide a data source for various details such as department, designation, profile image, etc. If not updated, this data might not be rendered correctly.

    2. Zluri supports selecting only one instance as the primary source for the data points. So it is advisable to select the source as primary, which is the source of truth for user information.

    3. When the same data flows to Zluri from multiple sources, Zluri displays the data fetched from the primary source selected in the dashboard. For example, Suppose the department data flows to Zluri from both Okta and Google Workspace, and Google workspace is selected as the primary source. In that case, Zluri will display the departments fetched only from Google Workspace.

  • Best Practices

    1. Select the primary source as the one which is your source of truth for employee data. I.e. the system where the user account data is updated first when a new employee joins or leaves the organisation (i.e. HRMS or SSO)

    2. Some of the data points can be maintained in multiple ways in a system (for example some organisations maintain their department-related information in org units in Google Workspace while some organisations maintain it in a user profile field in Google Workspace). Please select the right path, in this case, in the interface.

    1. Please reach out to your designated Customer Success Manager if you wish to fetch the information from any other integrated applications or custom fields from existing options.

    2. Please make sure that the primary sources for all data are set properly and reflect on the platform accurately before generating any reports or creating any workflows/automation rules.

Can’t find what you are looking for? Let us help you!

Onboarding Process (26)