01

Pilot setup

Your Workspace administrator installs Collabma, approves the exact domain and Group identities, and excludes security or access Groups.

02

Using Clean view

Open an approved Collaborative Inbox, review the disclosure, choose Enable, and use a shortcut only when Collabma shows one verified native action.

03

Returning to native

Choose Native view at any time. Google Groups remains available even when Collabma is disabled, blocked by policy or removed.

Before you begin

Pilot requirements

Chrome 120+

A current managed Google Chrome profile.

Workspace account

The primary Chrome profile domain must match policy.

Approved Group

The exact canonical address or alias must be approved.

Collaborative Inbox

Conversation history and Google’s native workflow controls must be available.

Troubleshooting

When Collabma does not appear

This usually means a safety gate is doing its job. Native Google Groups should remain usable.

Confirm the correct Chrome profile

The primary Chrome profile that is signed in, rather than an email alias, must belong to the Workspace domain approved by administrators.

Confirm the exact Group route

The current canonical Group address or alias must appear in the operational policy and must not overlap a security or access Group.

Close native menus and dialogs

Collabma does not offer a shortcut while a blocking Google Groups menu, listbox or dialog is open.

Use Native view and refresh

Return to Native view, refresh the Google Groups page and ask your administrator to verify the current pilot policy before enabling Clean view again.

Do not repeat an uncertain action

If Google’s final state is unclear, inspect the native assignment or status. Never click again merely to make sure.

Contact

Need help with the private pilot?

Include the Collabma version, Chrome version, route type, visible error and steps that led to it. Do not include message content, customer records, passwords or verification codes.

Email support