Start with your shared board.

1. Test the board with Google sign-in

You can test this before publishing or sharing the Team Bot. Your Google sign-in already gives you access to the board in this browser. No API key, local installation or source connection is needed to view it.

An empty board means no approved records have been published yet. It does not mean your sign-in failed.

2. Connect your personal bot when ready

The Team Bot provides the shared setup and walkthrough. Its secrets are shared, so never save your personal API key on the Team Bot. Open your own personal bot for source setup and publishing. A private chat with a shared bot is not a private credential store.

Your first Google sign-in creates a personal API key, shown here once. Copy it or download its private file, then use your personal bot’s private secret entry for UO_API_KEY. Do not paste it into ordinary chat. If the platform cannot confirm that secret storage is private to you, stop before saving it.

A new key does not revoke older keys. Existing saved keys can still be used until revoked or expired.

In your personal bot, ask: “Set up my personal Team Partnerships connection. Keep my credentials private. Verify my Google-linked identity over HTTPS using X-API-Key, then read the shared board. Do not connect sources or publish anything yet.” The bot must report the actual identity and connection result before continuing.

3. Connect sources separately

Only continue on a runtime private to you. Install the kit on your personal Grok Bot computer. Extract it and run python3 install.py with Python 3.11 or newer. It creates separate local stores with refresh disabled; installation does not connect Gmail, pair WhatsApp or publish data.

1. Gmail: use a separate, member-owned msgvault home and read-only consent. Only partnership Cc mail is acquired, with size and storage limits and no historical date floor.
2. WhatsApp: use your own authorized WACLI account and selected business chats. The kit does not pair a phone or start broad synchronization.
3. Meetings: select your own meeting IDs from Granola, Read.ai, Google Meet or another notes tool. Raw bodies remain local.

Your personal bot verifies the source account and exact source grant before refresh. Do not treat empty local stores as a successful source connection.

4. Approve one publication

Your personal bot shows the exact lead facts and summary to be shared. Approve one item, receive the stored receipt, then check the result on the board. Local refresh alone never publishes. A real-source pilot requires your source consent and an approved grant; synthetic tests do not complete those steps.

The Team Bot may explain non-secret results, but should not ask you to shuttle keys or raw logs between chats. Direct member-authenticated Team Bot access is pending a verified per-user connector.