Pilot setup
Your Workspace administrator installs Collabma, approves the exact domain and Group identities, and excludes security or access Groups.
Support
Collabma 1.8.4 is a private beta managed by administrators. Start with an approved Workspace profile and Collaborative Inbox, then verify every action in native Google Groups.
Your Workspace administrator installs Collabma, approves the exact domain and Group identities, and excludes security or access Groups.
Open an approved Collaborative Inbox, review the disclosure, choose Enable, and use a shortcut only when Collabma shows one verified native action.
Choose Native view at any time. Google Groups remains available even when Collabma is disabled, blocked by policy or removed.
Before you begin
A current managed Google Chrome profile.
The primary Chrome profile domain must match policy.
The exact canonical address or alias must be approved.
Conversation history and Google’s native workflow controls must be available.
Troubleshooting
This usually means a safety gate is doing its job. Native Google Groups should remain usable.
The primary Chrome profile that is signed in, rather than an email alias, must belong to the Workspace domain approved by administrators.
The current canonical Group address or alias must appear in the operational policy and must not overlap a security or access Group.
Collabma does not offer a shortcut while a blocking Google Groups menu, listbox or dialog is open.
Return to Native view, refresh the Google Groups page and ask your administrator to verify the current pilot policy before enabling Clean view again.
If Google’s final state is unclear, inspect the native assignment or status. Never click again merely to make sure.
Contact
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.