Skip to main content

Quick Start

Hana works inside Google Chat and is configured from the Hana Dashboard.

Hana is designed as an information agent: she ingests team knowledge, understands chat context, and helps convert questions into clear actions.

Setup Flow (Visual)​

Confused about what to ask Hana?

Read What Hana Is (And How To Use Her) first, then come back to setup.

Need Help? Reach Out Early

If installation, permissions, memory setup, or output quality is not working as expected, reach out early. Early guidance usually saves significant setup time.

Use Support Channels, FAQs, and Troubleshooting.

Before You Start​

  • You need a Google Workspace account.
  • Your Workspace Admin may restrict third-party app installation.
  • If Hana is blocked, ask your admin to allow the Hana app from Google Workspace Marketplace.

Install Hana in Google Chat​

You can install Hana from either Google Chat directly or Google Workspace Marketplace.

Option 1: Add From Google Chat​

  1. Open Google Chat.
  2. Open the target space.
  3. Open space settings.
  4. Go to Apps and integrations.
  5. Click Add apps.
  6. Search for Hana and add it.
  7. Wait for Hana's welcome message with dashboard login details.

Option 2: Add From Google Workspace Marketplace​

  1. Open Hana on Google Workspace Marketplace.
  2. Click Install.
  3. Choose install scope (org-wide or selected groups, as available to your admin role).
  4. Complete authorization prompts.

Complete Dashboard Setup​

  1. Open Hana Dashboard.
  2. Sign in with Google.
  3. Complete basic org setup.
  4. (Optional) Configure memory sources and org-level settings.

First Interaction​

Go back to your chat space and send:

@Hana hi

Then test one real workflow prompt, for example:

@Hana summarize this thread and list next actions with owners

Then test one knowledge-grounding prompt:

@Hana based on our recent decisions in this space, what should we prioritize this week?

First Week Plan (Teams)​

Use this rollout plan to get value from day 1 and avoid a "we installed it but nobody uses it" outcome.

Day 1: Install + Verify + Baseline Usage​

  1. Install Hana in your primary team space using the steps above.
  2. Confirm setup by sending:
@Hana hi
  1. Run these three baseline prompts in a real active thread:
@Hana summarize this thread and list decisions.
@Hana extract action items with owner and due date from this thread.
@Hana list blockers mentioned in this thread and group by owner.
  1. Document baseline quality in one internal note:
  • What was accurate.
  • What was missing.
  • What follow-up prompts improved output.
  1. If baseline quality is weak, contact support the same day for setup and prompting guidance.

See:

Day 2: Add Memory That Matters​

  1. Add 1-2 high-signal memory sources (SOP, policy, launch brief, project context).
  2. Prefer concise, current docs over bulk uploads.
  3. Test retrieval quality immediately:
@Hana based on our memory, what is our escalation policy for P1 incidents?
@Hana what does our launch checklist require before production rollout?
  1. If responses are weak, refine memory content and retry.

See:

Day 3: Standardize Prompt Patterns​

  1. Create 5-10 reusable team prompts for recurring workflows.
  2. Use objective + scope + time window format.
  3. Put templates in your internal runbook.

Prompt template:

@Hana <objective> using <scope> for <time-window>, and output as <format>.

Example:

@Hana summarize sprint blockers using this space for the last 7 days, and output as a table by owner.

See:

Day 4: Operationalize in Live Team Work​

  1. Require thread summaries at the end of major discussions.
  2. Require action-item extraction for project and incident threads.
  3. Use Hana for daily/weekly check-ins:
@Hana summarize updates in this space from today 9am to now by owner.
@Hana list unresolved blockers in this space this week.
  1. Assign one owner to enforce this cadence for the next 2 weeks.

See:

Day 5: Add Automation Entry Points​

  1. Add at least one report group for structured updates.
  2. If using external systems, start with one Hana API workflow (for example: create report messages or approvals).
  3. Validate end-to-end behavior in a test space before production-wide use.

See:

Day 6-7: Measure and Tighten​

  1. Review one week of usage:
  • Which prompts were most useful.
  • Which responses needed follow-up.
  • Which memory sources improved outcomes.
  1. Remove low-value prompts and keep only repeatable high-signal ones.
  2. Define your team’s "standard Hana workflows" (3-5 workflows max).

Week 2+ Operating Cadence​

  1. Weekly: refresh memory sources that changed.
  2. Weekly: review top prompt patterns and improve wording.
  3. Monthly: audit connectors/API workflows and remove unused ones.

Common Setup Issue​

If Hana appears in the space but does not respond correctly:

  1. Open Apps and integrations for the space.
  2. Remove Hana.
  3. Add Hana again.
  4. Retry @Hana hi.

OAuth / Permission Notes​

If Hana asks you to complete OAuth permissions, finish the flow and approve all required scopes for enabled features. If permissions were partially granted earlier, you can manage and expand scopes from Dashboard → Settings → OAuth Scopes, then retry.

Choose Your Hana Use Case​

Hana supports two use-case profiles:

  • BUSINESS_ASSISTANT (default): recommended for team and org workflows.
  • PERSONAL_COMPANION: recommended for personal one-to-one assistant style interactions.

Example:

@Hana set hana use case to BUSINESS_ASSISTANT
Last updated on by nav