The nima admin panel

What the web app at app.getnima.io does today: sign-in, onboarding, Integrations and Settings, and what it deliberately does not do.

The nima admin panel is the web app at app.getnima.io. It has four jobs: sign in, set up a workspace, connect integrations, and manage settings. You work the pipeline itself (signals, beacons, specs, delivery) in Slack, over MCP and over the REST API, not in the web app.

On for every workspace. Some screens are visible only to workspace owners and admins, as noted below.

Signing in to nima

You sign in to nima with a Google account. The sign-in page has one button, "Continue with Google". Any Google account can sign up: there is no domain allowlist, no email-and-password login, no SSO and no SCIM.

A session access token lasts 15 minutes and is refreshed silently. Each refresh starts a new 7-day window, so you stay signed in as long as you use nima at least once every 7 days; after 7 days without use you sign in again. nima keeps one web session per person: signing in on a second browser signs the first one out, and can end both, so sign in again if that happens. API keys and MCP tokens are separate credentials; see authentication.

Onboarding a new workspace

Onboarding is a three-step wizard that runs the first time you sign in. Steps 2 and 3 can be skipped.

Name your workspace. Enter a name of at least two characters. nima generates the URL slug for you.
Add to Slack. Install the nima Slack app. This is where most of your day-to-day work with nima happens. See nima in Slack.
Connect tools. Connect GitHub, Linear, Jira, HubSpot, Notion, Granola, ClickUp, Sentry and PostHog, in that order. A collapsible "Bring your agent" card holds a paste-in prompt for connecting a coding agent to https://mcp.getnima.io/mcp. GitHub is optional, not required to finish.

When you leave step 1, nima creates the workspace and you become its owner. If your sign-in email is on a company domain, nima guesses your website from it (for example https://acme.com from you@acme.com) and starts reading that public site in the background, adding what it learns about your company to the knowledge graph. Public mail providers such as Gmail, Outlook and iCloud are skipped, so no website is guessed for them. Finish takes you to Integrations.

Create another workspace

To add a second workspace, use the create-workspace action in the top bar. It opens the wizard at /onboard?new=1, which skips the guessed website and starts at the workspace step.

One person can own at most 3 workspaces; the limit and how several workspaces work are in belonging to several workspaces.

The Integrations page

The Integrations page is the home screen of the admin panel, at / and /integrations. It shows one tile for each integration, labelled connected, paused, needs reconnect, not connected or coming soon (the coding-agents tile reads set up).

Open a tile to see what you can do with it:

Connect starts the OAuth round trip, or asks for an API key for the integrations that use one. A tile that lost access shows Reconnect instead.
On / Paused is a switch on a connected tile. It records whether you consider the integration active. Turning it to Paused shows the tile as paused, but it does not stop nima from reading or acting through that integration. The confirmation dialog says pausing stops syncing; it does not. To actually stop, use Disconnect.
Disconnect removes the connection after you confirm.

Only owners and admins can see this page, because connecting a tool is workspace-level configuration. A member who opens it is sent to Settings, General. The integration-specific setup for each tool is on its own page, listed under integrations.

Settings tabs in the admin panel

The Settings page has one tab per topic. A member sees General, Members, API keys and Grouping; owners and admins also see Billing, Usage and Account. A tab you cannot see sends you back to General.

Tab	Who sees it	What it holds
General	Everyone	Your profile (name, email), the workspace name and slug, and your role. Read-only.
Members	Everyone; write controls for owners and admins	The member list, invite by email with role admin or member, pending invitations with Resend and Revoke, change role, remove a member. See members and roles.
API keys	Everyone	Create, rotate and revoke your own personal keys; owners and admins can also list, rotate and revoke every key in the workspace. The scopes ticked by default are `knowledge:read` and `signals:read`. Expiry is 30 days, 90 days (default) or 1 year. An optional list of allowed IPs or CIDR ranges restricts where a key works. See authentication and scopes.
Grouping	Everyone; the control is for admins	One select, "Signals per beacon", with the values 2 or 3. It has no effect today (next paragraph).
Billing	Owners and admins	The plan card, seat cap and Upgrade or Manage billing buttons. See Billing status.
Usage	Owners and admins	LLM cost for the workspace over 7, 30 or 90 days (30 by default): totals, per day and per feature, plus seats used against the plan's cap. Read-only: there are no quotas or alerts.
Account	Owners and admins	Rename the workspace and change its URL slug (lowercase letters, numbers and hyphens); the workspace ID, plan, member count and creation date; and, for the owner only, a danger zone with "Delete workspace" and "Cancel deletion".

The Grouping setting is stored, but nima's automatic beacon placement no longer reads it, so changing it does not change how signals group. Do not use it as a control. How placement works is in how nima decides.

Delete a workspace from Account settings

To delete a workspace, the owner opens Account settings, uses "Delete workspace" in the danger zone and types the workspace slug to confirm. Deleting starts a 7-day hold that "Cancel deletion" clears; the rules are in deleting a workspace.

What is not in the admin panel

The admin panel has no pages for the pipeline, and no controls for several workspace features. Each one lives somewhere else.

You are looking for	It is not in the admin panel	Where it lives instead
Signals, beacons, specs, delivery, kanban, timeline, codebase	Those pages are retired. Old links, including links in Slack ship notices and MCP results, redirect to Integrations.	Slack, the MCP tools and the API reference
Copilot chat	There is no chat panel in the app.	Mention `@nima` or DM it in Slack. See nima in Slack
Promote a beacon, comment on a spec	No button or inline comments.	`POST /v1/beacons/:id/promote` and the spec comment routes, called with a signed-in session. API keys and MCP tokens get a 403 on these routes, and no MCP tool promotes a beacon or comments on a spec. See the beacons API and the specs API
Creating a webhook source	No page creates one.	`POST /v1/signal-webhooks`, called with a signed-in owner or admin session. See webhooks
Switches for watches and outbound actions	No control.	`PATCH /organizations/settings` with an owner or admin session, or ask the nima team. See what is on in your workspace and workspace settings
Hosted compute for agent operations	No control.	`PATCH /v1/agent-compute` (owner or admin session, or a key with `integrations:write`) or the `update_agent_compute_settings` MCP tool, after the nima team grants the plan feature and sets pricing. See hosted VMs

Members cannot connect integrations and do not see Billing, Usage or Account. An API key or MCP token cannot change workspace settings, manage members or delete a workspace: those routes accept only a signed-in web session.

Billing status: nobody is charged yet

Billing is not enabled yet, and nobody is charged. The Billing tab and the Upgrade button exist, but payment is not connected, so an upgrade cannot complete. Every new workspace starts on the Free plan with a 3-seat cap, and the nima team changes a workspace's plan on request. The Usage tab shows what your workspace spends on AI so you can see the cost before billing starts.

The nima admin panel

On this page