How to Invite a Teammate using Google Directory?

Importing from Google Directory pulls your existing Google Workspace users into SyncSignature with their names, job titles, departments, and aliases already filled in. It is two steps: connect Google Workspace under Integrations, then import the users you want from TEAMMATES.

Importing a teammate is not the same as inviting them. The import creates the teammate and generates their signature. The invite hands them a login. For most teams, the import alone is all you need.

Import and invite are different things

This is the part worth getting straight before you start clicking.

Step	What it produces	Who needs it
Import from Google Directory	A teammate record with directory fields filled in, plus a signature once they are in a group	Everyone whose signature you manage
Install signature	The signature placed in their Gmail account by you, as admin	Everyone on Google Workspace
Send invitation	A login to your SyncSignature workspace	Only Managers and people who edit their own details

If you deploy with Install signature, most of your team never needs to log in at all. Their signature appears in Gmail without them doing anything. Invite the people who change their own photo or phone number, plus anyone acting as a Manager.

Before you start

Requirement	Where it lives	Notes
Google Workspace super admin	Google Admin console	Connecting the integration needs super admin consent
The SyncSignature app	Google Workspace Marketplace	Install it before connecting
Owner or Manager role	Your SyncSignature workspace	Teammates cannot import or invite
A saved template	TEMPLATES	Imported teammates get signatures only from a group's template
A group to import into	GROUPS	A teammate with no group has no signature and cannot be invited

Connect Google Workspace under Integrations

Install the SyncSignature app from the Google Workspace Marketplace.
Open Integrations in SyncSignature and choose Google Workspace.
Sign in with a super admin account and approve the requested access. A standard user account will connect but return an empty directory, which is the single most common setup mistake.

What you are approving is narrow, which is useful to know when someone asks. SyncSignature requests read access to the Admin SDK Directory API (users, organizational units, groups, and profile fields) plus write access to Gmail's sendAs resource, which is what lets it place a signature. It does not request mailbox read or send scopes, never sees message content, and mail is not routed through SyncSignature at any point.

Import users from your Google Directory

Open TEAMMATES and choose the option to import from Google Directory.
Review what loads. Your domains, domain aliases, users, and each user's aliases all populate. You do not have to import everyone at once.
Select the users you want. Tick the people whose signatures you are going to manage.
Select their aliases. Each alias is treated as an additional teammate in SyncSignature, which is what lets sales@yourcompany.com and support@yourcompany.com carry different signatures for the same person. Skip the aliases nobody sends from. Each alias you tick becomes its own seat once it lands in a group, so a 30 person team where everyone has one role alias is a 60 seat workspace rather than a 30 seat one. See how seats and licenses work.
Import. Names, job titles, departments, phone numbers, and photos come across from the directory and populate the merge tags in your template: {{name}}, {{title}}, {{department}}, {{phone}}, {{photo}}.
Add the imported teammates to a group. The signature is generated the moment they land in a group that has a template assigned.
Install the signatures. From inside the group, select the users and click Install signature. This writes the signature into Gmail for each selected address. It works on Gmail web, iOS, and Android.

Turn on Auto install for this connection under Integrations and step 7 stops being something you do. It is off by default and set once per integration. With it on, both template edits and newly synced users install themselves.

Once teammates exist in the workspace, inviting them is the same flow as any other invite:

Confirm each person has a group assigned. Without a group, the invite cannot be sent.
Select them in TEAMMATES and click Send Invitation.
Assign Manager or Teammate. A Manager can manage templates, teammates, and signatures in this workspace. A Teammate can only manage their own details and copy their own signature.

They can accept by signing in with their Google account, since they already have one. Do not send invitations to alias entries. An alias is a signature holder, not a person with a login.

Why importing beats typing addresses by hand

No typos in the addresses you install to. A mistyped address means a signature installed nowhere, with no error to tell you so.
Job titles and departments arrive correct. Merge tags fill from real directory values, not from a spreadsheet.
Aliases come along automatically. Finding every alias by hand across a 40 person company is its own afternoon.
The directory stays the system of record. Changes reach signatures on the next sync cycle, generally within 5 to 10 minutes on the SyncSignature side, plus whatever delay Google adds.

It keeps working after the first import. Your organizational units sync as groups in SyncSignature, so a new hire created in Google Workspace is picked up on the next sync and lands in the group matching their OU. If their OU is not one you selected, they fall into the default group. Either way a signature is generated for them without anyone re-running the import or touching TEAMMATES.

One honest limit on the wording: this is a directory read, not SCIM provisioning. SyncSignature creates the new hire's signature, not a login for them. Invite them separately if they need to edit their own details. More detail is on the directory sync page.

Common issues and fixes

Issue	Cause	Fix
No users appear after connecting	Connected with an account that is not a super admin	Reconnect under Integrations using a Google Workspace super admin account
Users imported but nobody has a signature	The imported teammates are not in a group	Add them to a group with a template assigned in GROUPS
Cannot send an invite to an imported user	No group is assigned to that teammate	Assign a group first, then send the invite
Job title or department is blank in the signature	The field is empty in Google Directory	Fill it in the Google Admin console, then let the next sync pick it up
An alias has no signature in Gmail	The alias is not set up in Gmail as a "Send mail as" address, or SMTP relay is not configured	Add the alias in Gmail, then configure SMTP relay under Apps > Google Workspace > Gmail > Routing
A new hire has no signature	Their organizational unit is not one of the units you synced, and no default group is set to catch them	Confirm the OU is selected on the Google Workspace connection under Integrations, or set a default group so unmatched users still get a signature

Email signatures for aliases in Google Workspace covers the Gmail and SMTP relay setup aliases need.
Install email signatures to Google Workspace walks through deploying from inside a group.
Invite teammates by email is the manual path when you are not on Google Workspace.
What are groups explains the template to group link that generates signatures.

Still stuck? Email support@syncsignature.com and include your Google Workspace primary domain and the admin email address you used to connect.