Skip to main content
This guide is for an organization’s IT administrator. It connects ParleHub to your Google Workspace in two parts:
  1. Single sign-on (SSO) — let your team sign in to ParleHub with their Google Workspace accounts.
  2. Google Drive storage — let project agents read and write files in your Shared Drives.
Do them in this order. SSO comes first because it establishes the link between ParleHub and your Google Workspace domain that Drive then reuses.
You’ll need: a Google Workspace Super Administrator (or an admin with the Security and Drive privileges) to trust the app and grant Drive access. In ParleHub you must be an Org Admin.

​
Part 1 — Single sign-on with Google

You allow your users to sign in to ParleHub with their Google Workspace accounts instead of a separate ParleHub password. Anyone in your organization whose email matches your domain can then sign in with Google.
1

Note your domain

This is the domain your team signs in with, e.g. contoso.com. ParleHub uses it to recognize your users and route them into your organization.
2

Trust ParleHub for your organization

In the Google Admin console → Security → Access and data control → API controls → Manage third-party app access, choose Configure new app → by OAuth Client ID, enter the ParleHub Client ID (your ParleHub onboarding contact provides it), and mark it Trusted. This lets your users sign in to ParleHub and approve access without being blocked by your app-access policy.
3

Configure the connection in ParleHub

Go to Org settings → Single sign-on, choose Google, and enter the Email domain your users sign in with. Then toggle Enable single sign-on on.
4

Test it

Sign out, then on the ParleHub login page enter a Workspace email address. A Sign in with Google button appears. Complete the Google prompt — you should land back in ParleHub, signed in.
New users: the first time a colleague signs in with Google, ParleHub creates their account automatically and places them in your organization — as long as their email domain matches and you have an available seat.
How users are matched: sign-in is routed by the email domain, not the account type — anyone whose verified Google email is on your configured domain can sign in, whether it is a managed Workspace account or not. Personal @gmail.com addresses cannot sign in to your organization because gmail.com is not your configured domain.
Single sign-on requires a Team plan or higher. If your plan is downgraded, Google sign-in stops working at the next login and users fall back to email/password.

​
Part 2 — Google Drive as project storage

ParleHub accesses files using its own application identity, scoped to only the Shared Drives you grant it — never your whole Workspace. The agent can then read and write project files even when no one is actively online. Deleted files go to your Drive trash, where your normal retention and recovery rules apply.
1

Pick (or create) a Shared Drive

For example a Shared Drive named Client Delivery. Using a Shared Drive rather than a personal My Drive folder is what keeps ParleHub’s access scoped and easy to audit.
2

Grant ParleHub access to that Shared Drive

Open the Shared Drive in Google Drive → Manage members, and add ParleHub’s service account email (your ParleHub onboarding contact provides it, e.g. parlehub-drive@…iam.gserviceaccount.com):
  • Viewer — the agent can read files.
  • Content manager — the agent can read and write files.
Repeat for each Shared Drive you want a project to use. Access is limited to exactly the drives you add ParleHub to.
3

Connect the Shared Drive to a ParleHub project

Open the project → Files (or Project settings → Storage), choose Google Drive, and pick the Shared Drive from step 1 and an optional sub-folder. Paste the URL of the Shared Drive itself — its root, not a sub-folder inside it.
4

ParleHub verifies the connection

It lists the drive’s root folder before saving. If it cannot reach the drive, you see an error — the most common cause is that step 2 has not been completed for that drive yet.
Files the agent creates appear in that Shared Drive; files your team adds there are visible to the agent’s tools.
Tenant reuse: if you already set up single sign-on in Part 1, ParleHub already recognizes your Workspace domain — Drive connects to the same Google organization.
Broader access (optional): if you need the agent to reach files beyond Shared Drives, ParleHub also supports Workspace domain-wide delegation, which your Super Administrator authorizes in the Admin console. Ask your ParleHub onboarding contact — most organizations are best served by per–Shared Drive access above.

​
Troubleshooting

Still stuck? Contact ParleHub support with your organization name and the Shared Drive you are connecting.