Skip to content

Get started

InHive is built so the first useful hour is not “recreate your Monday board by hand.” You create a hive, invite people, point a project at what you already have, and approve what InHive proposes.

These are different actions. Mixing them up is the most common first-day mistake.

  1. Open Create your hive on the login screen (register).

  2. Enter name, email, and password — or Continue with Google. Registration always creates a new organization. You become its admin. A role field, if you see one, is ignored.

  3. Confirm the email InHive sends. Until you do, the hive is not usable.

  4. You land on the dashboard of an empty hive. Next: invite people, then add a client and a project.

Open the invite link in the email (or the link a manager copied from People). Accept it with a password, or Continue with Google using the same address the invite was sent to. That joins the existing hive. It does not create a second one.

If the product is on waitlist or invite-only:

  • Ask your admin for an invite, or
  • Join the waitlist if it is offered. You will get a one-time signup email if that address is approved.

You need three things before the board is useful: people, a client, and a project with material.

  1. Invite the team. Open People in the left rail. Managers send invitations by email. The link is also copyable if mail is slow. Seats follow your platform plan — billed per active member after the trial.

  2. Add a client. Open Clients (managers). Company name, a main contact person, and their email are required. This is the company you will invoice later, not a login.

  3. Create a project under that client from Projects. Give it a name. Open it. You are now on the page people live on.

  4. Do not rebuild the board from memory if the work already exists somewhere:

    • Monday.com — Organization settings → Plugins → Monday. Wizard maps people and boards. Available on every plan. See Plugins.
    • Files you already have — open Documents on the project, upload the brief, notes, and a kickoff transcript. Then use Propose from knowledge. InHive drafts features, tasks, and open decisions. You approve what stays. See Documents.
    • Another tool (Linear, Jira, Asana, …) — a coding agent can run a one-shot import. See Agents.
PlaceWhen to open it
ProjectsThe engagement itself — tasks, documents, time, AI
My Work“What is assigned to me, overdue first”
Schedule“What is late across the hive” (managers)
DashboardMorning scan: pulse and attention (quiet clients, stalled work)
TicketsClient requests. A ticket is still a task
ChatProject rooms, DMs, calls (Studio+)
PeopleRoster, invites, Teams
Avatar menuAccount, organization settings, this help

The project page keeps tasks in view. Features, documents, time, and the assistant stay closed until you open them. That is intentional.

  • Set task statuses and labels if the hive’s language is not “To do / Doing / Done.”
  • Put hours on a rate card before anyone logs time you intend to bill.
  • Chat is on for Studio, Team, Enterprise, and the trial — there is nothing extra to install. Optional: the desktop app for a dock icon and InHive-attributed banners.
  • A manager should finish AI settings (provider and key) before anyone relies on Ask or the assistant.
  • Connect Agents only after the project has a brief or a reviewed spec. Empty knowledge makes an agent guess.
  • Hive — your organization.
  • Platform plan — Studio, Team, or Enterprise. That is the subscription. A new hive starts on a 14-day trial.
  • AI settings — provider, key, model tier, monthly token limit. There is no separate “AI plan.” See AI settings.

Next: your account, or go straight to projects.