Frequently Asked Questions

A regularly updated list of the most popular questions about Lanteria HR functionality. Use Ctrl + F for search.

Yes, a full list of integrations is available here: Integrations

Yes, click for the details: Technical Prerequisites Checklist 

Yes, you can read more about it here ==> Datasheet Lanteria

Yes, and the Lanteria HR App is a great self-service tool. Click for more details: Mobile App.

Storage is almost unlimited.

Lanteria’s HR solution is represented as an application in Azure that is displayed to end-users under My Apps in Office 365 and can be assessed without the additional requirement to enter credentials once they are logged in to Office 365.

Yes! Office 365 is one of Lanteria's major integrations. Read more about it here.

Yes, you need at least one SharePoint server and one SQL server or use hosting services provided by Lanteria.

No, first Lanteria should be implemented (populate org structure, create job roles, employee records, etc.). This process usually takes 3-5 months.

Yes, for on-premises installations only (this could be solutions to customize SharePoint forms, extend SharePoint Designer Workflows, etc).

Yes, click here for more information.

Yes, you need at least one SharePoint server and one SQL server or use hosting services provided by Lanteria.

No, first Lanteria should be implemented (populate Org structure, create job roles, employee records, etc.)

Any type which is supported by SharePoint (Local Active Directory, FBA, Trusted Providers - O365, ADFS).

Yes, after you configure the connection to an SMTP server (applicable for on-premise deployment only, if hosted by Lanteria no actions needed).

Yes, it could be used to pull data directly from the site, or from the shadow Lanteria SQL database.

Yes, you can build cloud flows but first On-Premise Data gateway should be configured.

This is an internet-facing site provided with Lanteria Recruiting module, it allows candidates to apply for open job openings. Click here for more information.

Yes, if you have the appropriate permissions (HR Admin).

In general, it allows to create custom lists and document libraries and store additional employee-related documents or other data there, use custom lists in performance reviews, etc. For on-premises deployments and existing integrations, it allows you to forget about creating employee records for new joiners manually. For cloud deployments - integration with MS Azure AD also allows automating the employee creation process. Another positive thing about SharePoint is the ability to use SharePoint PowerShell to manipulate the data.

Yes, you surely can! The system is flexible and can be customized. You can use your logo, color scheme, e-mail signatures, and templates, etc.

Yes, migration from SharePoint Server 2013 to SharePoint Server 2016 and from SharePoint Server 2016 to SharePoint Server 2019 is possible. Migration from 2013 directly to 2019 is not supported.

Yes, hybrid hosting is possible.

Yes, you can always request custom development.

Yes, Lanteria has inbuild integration with a variety of external systems. Additional settings should be applied.

Yes, but for performance and reliability reasons we recommend keeping the SQL database separately from the Front End server.

Yes, it is possible to deploy Lanteria HR on the existing SharePoint server as a new Web Application. Separate SharePoint server recommended for performance reasons.

Yes, the content database doesn`t need a separate SQL DB server.

Yes, Lanteria has an inbuild SharePoint Learning Kit and SCORM Engine.

Yes, Lanteria provides several options for integrating with SharePoint Online.

If you don’t see the answers you need here, please don’t hesitate to contact us