Skip to main content
Use this checklist to make Entelligence useful without granting broader access than the pilot requires.

​
Decide scope and ownership

Record:
  • The workspace owner and backup administrator
  • Pilot teams and repositories
  • Products included in the pilot
  • Approved Git, Slack, project-management, observability, documentation, and AI-tool connectors
  • Who can change repository settings, create keys, manage billing, or run write actions
  • Success criteria and review date

​
Connect the minimum sources

Open Connectors to see the connectors available to your workspace.

​
Configure people and mappings

In Settings → Team:
  • Invite pilot members as Member unless they need administrative access.
  • Create teams before assigning team-level analytics or reports.
  • Set an expiry for email invitations and shareable invite links.
  • Map users for Cursor, Claude Code, Codex, Linear, and Slack where those sources are used.
  • Rotate or revoke an invite link after the intended group has joined.
The invite-link screen warns that joins can affect billing in the following month. Review seat and plan information in Settings → Billing before sharing a broad link.

​
Validate authentication and repository access

  • Confirm the Git-provider token or app is connected under Settings → Auth.
  • Synchronize repositories under Settings → Code Management.
  • Enable only the pilot repositories.
  • Confirm the app has the read and write capabilities required for the feature you enable.
  • Test private-repository visibility with a non-admin pilot member.

​
Configure Slack intentionally

In Settings → Slack Notification:
  1. Connect the approved workspace.
  2. Add the Entelligence bot to each destination channel.
  3. Map Entelligence members to Slack users.
  4. Configure only the notification types required for the pilot.
  5. Send a test report or trigger a test Pulse.
Channel membership and visibility determine what the bot can read or where it can deliver messages.

​
Protect credentials and spend

  • Create API keys only for a named CLI or MCP owner.
  • Store keys in an approved secret manager for CI.
  • Test key rotation with a non-production client.
  • Review Model Router billing mode, balance, limit, and auto top-up.
  • Review plan, included usage, seats, payment state, and invoices in the app instead of copying prices into runbooks.

​
Establish governance

Before expanding the pilot, document:
  • Which analytics are used for coaching and enablement
  • Who can see individual and team-level views
  • Whether leaderboard visibility is appropriate
  • Which Ask Ellie and Reactor actions may write to external systems
  • Approval rules for generated fixes
  • Retention, audit, and incident-escalation requirements agreed with Entelligence

​
Verify the rollout

A pilot is ready when:
  • Connectors show healthy authentication.
  • Pilot repositories and members are visible.
  • One review or product workflow completes successfully.
  • Slack delivery reaches the intended channel or user.
  • A pilot member cannot access an out-of-scope repository.
  • The owner knows how to disable the feature, revoke access, and contact support.

​
Next step

Follow the quickstart, then use workspace administration for the complete control map.