Guide
Connect Kopexa to Google Workspace: Plan and test SAML SSO
Plan and test Google Workspace as Kopexa’s SAML identity provider. Domain, metadata, user access and the distinction from data import explained.


If employees should sign in to Kopexa with managed Google accounts, SAML SSO is the appropriate connection type. It does not automatically import Drive files or Google security evidence.
These steps combine the documented SAML settings of both systems. Acceptance tests check email mapping, user access and Space permissions before approval for regular operation.
Prepare the domain and access
First verify your email domain in Kopexa. The domain setup documentation describes DNS verification and activation consequences. Ensure every affected user can be enabled for the new application in Google.
Plan MFA in Google and name a configuration owner. After Kopexa SSO activation, identity-provider sign-in applies to all users of the domain.
Create a custom SAML application
In Google Admin, create a custom SAML app under Apps. Download Google’s IdP metadata. Use Kopexa’s entity ID https://id.kopexa.com/sso/saml/metadata and ACS URL https://id.kopexa.com/sso/saml/acs as service provider values.
Google’s custom SAML application guide explains Name ID and attribute mapping. Kopexa needs the email address. Check the value actually transmitted and the expected mapping; a display-name setting that looks similar is insufficient.
Enter metadata in Kopexa
Open SSO settings for the verified organisation domain and enter Google’s XML metadata. The signing certificate is read from it. Enable the application for intended users or organisational units first.
Activate SSO only during the agreed transition window. Existing Kopexa password accounts on the same domain are affected too. Resolve unclear mappings before switching using the SAML response and current product documentation.
Test authentication and authorisation separately
Test an authorised user, a user not enabled for the application and a new user. Then check organisation membership and Spaces actually visible. Successful authentication does not automatically mean correct business access.
Auto-join can create organisation membership during SSO. It does not replace careful Space permission assignment. Record this distinction in your access control policy.
Google identity and Kopexa account must align
Pay particular attention to the email address actually transmitted. Alias, primary address and display name are different. An account can look correct in Admin while sending another value in the SAML response.
Use an authorised existing user and verify the expected Kopexa identity. Then test the intended path for new users. Decide beforehand whether organisation membership should arise through auto-join or invitation.
The three main acceptance questions
| Test | Expected outcome |
|---|---|
| Enabled account | Sign-in and business access match the intended role |
| Account not enabled | No unexpected access is created |
| Account with a changed address | Identity mapping is deliberately assessed rather than assumed seamless |
Test the actual effect of an address change through the agreed procedure. This guide is derived from both systems’ documentation; it does not replace an end-to-end test of your production domain.
Take over operation
Record certificate expiry, owners and change procedures. Import new metadata into Kopexa on time and retest sign-in. When someone leaves, assess the actual effect of your blocking and session procedures.
For desired Google data import, separately establish available interfaces, permissions and scope. Document verified SSO setup as evidence for the corresponding measure.
Quick answers
Frequently Asked Questions
Still have a question? Find the answers here.
Does Google SSO automatically transfer Drive documents into Kopexa?
No. SSO handles authentication. Document or security-data import is a separate integration case whose availability and permissions need assessment.
Sources
- Set up a custom SAML application — Google [Accessed ]
- Organisation domains and SAML SSO — Kopexa [Accessed ]