Texlaculture HRMS + Google Workspace

What this integration does

A large share of Indian startups, services firms, and modern mid-market companies run their day-to-day on Google Workspace — Gmail for mail, Calendar for scheduling, Drive for documents, Meet for calls. Treating Texlaculture HRMS as a separate island next to those tools creates friction for every employee, every day. The Google Workspace integration removes that friction across three surfaces: identity, calendar, and document storage.

Sign-in is handled through Google as the identity provider, leave and interviews appear on the right calendars automatically, and HR documents — offer letters, signed appointment letters, Form 16s, ID proofs — can be stored in a Drive structure your IT admin controls.

What gets synced

• Single sign-on via SAML 2.0 or OpenID Connect with Google as the identity provider
• Automatic user provisioning and de-provisioning when employees join or exit
• Two-way calendar sync — approved leave blocks the employee's Google Calendar
• Interview invites with Google Meet links generated from the recruiter dashboard
• Holiday calendar published to a shared Workspace calendar
• Birthday and anniversary events surfaced on a team calendar (optional)
• HR documents stored in Google Drive folders mapped per employee
• Drive permission management aligned with Texlaculture HRMS roles

How it works

Identity is configured by your Workspace admin from the Google Admin console — either as a SAML application or as an OIDC client. Once set up, employees log in to Texlaculture HRMS by clicking "Sign in with Google"; account creation can be automated so every new Workspace user gets the right Texlaculture HRMS profile, and removal from Workspace de-activates the Texlaculture account.

Calendar and Drive use Google's standard APIs over OAuth 2.0. For calendar, the integration writes events into the affected employee's primary calendar and into any team calendar your HR admin configures, with the right visibility — leave events are marked free/busy without exposing the leave reason. For Drive, the integration stores files in a Workspace-owned folder structure, so documents continue to be governed by your existing Drive DLP and retention policies.

Use cases for Indian businesses

For Indian startups standardised on Google Workspace, the integration is what makes Texlaculture HRMS feel like a native part of the company stack. Employees never see a separate password; new hires log in for the first time using their Google account on day one. Recruiters scheduling interviews generate Meet links straight from the ATS screen, so candidate experience is one click rather than several copy-pastes.

For HR teams, Drive-based storage solves a quiet but important problem: where do confidential employee documents actually live, and who can access them. Texlaculture HRMS keeps a structured per-employee folder in Drive, sets the right sharing permissions, and updates them as employees move between teams or exit — so document access never gets left behind.

Frequently asked questions

Can we enforce SSO and disable password login?

Yes. Once Google SSO is configured, admins can require all users to sign in through Google and turn off local password login entirely, so account security is governed by your Workspace policies and MFA.

What does the calendar sync share?

Approved leave is written to the employee's calendar with free/busy marking and a neutral title; sensitive leave categories are not exposed. Interviews include the candidate and the Meet link only on the relevant calendars.

Where do documents physically live?

In your Google Drive. Texlaculture HRMS reads and writes files in a Workspace-owned folder structure, so the documents are subject to your Drive sharing controls, retention policies, and DLP rules — not held inside a separate vendor silo.

Does this work for groups using Google Workspace alongside another IdP?

Yes. Many groups federate Google Workspace behind a primary IdP like Okta or Microsoft Entra ID. Texlaculture HRMS supports that pattern — sign-in still works, and Drive and Calendar integrations continue to use Workspace as the data plane.