Skip to main content

People in a workspace

A workspace has exactly one owner, whose first sign-in created it, and any number of admins, developers and viewers, up to its plan’s member limit. The owner and admins invite people with a shareable link, choose the role each one joins with, and later change a member’s role or remove them in Settings → Members. Team members covers inviting, removing, transferring ownership and switching between workspaces. Settings → Members and Settings → Plan & billing → Your access show your role. Nobody can grant a role above their own. Only the owner can make someone an admin, an admin cannot change the owner or their own role, and owner is never granted: it moves only by transferring ownership. The two credentials that act for a person are held to the same roles. An API key carries a role, and a connected agent is clipped to one by the access you grant it. Either one is also capped by its person’s current role, so changing someone’s role changes what their keys and agents can do on the next request.

Roles

Each role can do everything the role below it can: A member role, from before these four existed, reads as viewer. Single sign-on through your own identity provider (SAML or OIDC) is planned and not available yet, on any plan: Settings → Single sign-on says Coming soon. People sign in with an emailed code or with GitHub.

How you signed in

The account panel, your profile in the console’s top bar, shows Signed in with and the method this session used, such as Emailed code or GitHub. It also says what guards the account: anyone who can read your email can sign in with an emailed code, whichever method you used, so your account is as safe as your inbox. Protect that mailbox with its own two-step verification. Hookie does not offer multi-factor authentication (an authenticator-app step) yet. If an account is ever asked for one, sign-in stops with mfa_required and the message that this sign-in page does not support it yet; contact support@hookie.ai. Over the API, GET /admin/api/me reports the method as signInMethod (see API reference).

API keys

An API key (hk_…) lets a system with no browser, such as a CI job, a script or your own backend, call the admin API and the hosted MCP server at /mcp. Owners and admins create them in Settings → API keys, and only a person signed in to the console can: an agent or another key cannot.
  • A key acts as the person who created it, and its role, viewer, developer or admin, is a ceiling on that person’s role. There is no owner role for a key, so billing is out of its reach. Inviting and member changes are too, at every role. If its creator leaves or is removed, the key stops working.
  • A key can be limited to one project, to an expiry date, and to an IP allowlist.
  • A key is shown once. Hookie keeps only its SHA-256 hash. Revoking a key stops its next request.
API keys covers creating, using and revoking them.

Connected agents

A connected agent is a coding agent, such as Claude Code, Cursor or any MCP client, that you connect to https://app.hookie.ai/mcp over OAuth. It signs in as you, through WorkOS AuthKit, and then holds a token it refreshes on its own: there is no key to paste anywhere. The Connect agent button in the console’s top bar opens Connect an agent, with the URL and the setup steps. What it may do is decided separately, by you, in Settings → Connected agents. A newly connected agent can only read. Change access gives it one of three levels, each including the one before: An agent’s authority is your own role narrowed to the level you granted, whichever is lower. A change applies on its next request, with no need to reconnect. Revoke cuts it off on its next request too, even though its token is still valid, because Hookie checks the grant on every call. At every level, an agent cannot touch billing, invite people or change who the members are, manage connected agents, create API keys, or reveal or rotate a destination’s signing secret. It can read the member list at hookie:read. Everything it does is written to the audit log with you as the actor and the agent’s client id beside it. Connected agents lists every tool and what each level unlocks.

The same ladder

API keys and agents share one ladder, so the same words mean the same thing everywhere: A call above what a credential holds is refused with 403. For an agent, the answer names the scope the call needs and links to Settings → Connected agents, so you can widen it.

Other credentials

Three more credentials exist, and none of them acts for a person or reaches the admin API:
  • An ingest key (ik_live_…) sends events into one project, and tails its live stream. See Endpoints and ingest keys.
  • A Data API key (hdk_…) reads the datasets and columns one project exposes. See Data API.
  • A portal token lets one of your customers into your customer portal.