After you install

The first hour as an administrator. Connect your repository, set up a project, add your people, and run your first piece of work.

A new Eido Build starts with one admin, which is whoever installed it, and nothing connected. Work through these in order.

Everything in the steps below starts from Admin.
Everything in the steps below starts from Admin.
  1. Connect your repository host

    In Admin → Integrations, connect GitHub or Azure DevOps.

    • GitHub is a GitHub App that your organisation owns.
    • Azure DevOps uses a managed identity.
  2. Decide where agents run

    In Admin → Workbenches, check the workbench your projects will use.

    • For a Foundry workbench, deploy the models you want in Foundry.
    • For an Anthropic workbench, paste an Anthropic API key in Admin → Integrations.

    Set a monthly budget while you are there. See Costs and budgets.

  3. Set up your project

    In Admin → Projects, point the project at its repository and choose how it ships. Write the project’s description, because every agent reads it. See Projects.

  4. Add your people

    In Admin → Teams, set up your teams. In Admin → Users, add each person, give them their projects and put them in their teams. See Users and permissions.

  5. Check the workflows

    A new project has the stock workflows. Open them in Admin → Projects → Workflows and check which teams take part in and approve each stage. See Workflows.

  6. Run something small

    Raise a small, real enhancement, approve it in Triage, and follow it through. See Your first work item.

Worth doing in the first week#

Set up emailSo that people are told when they are assigned something. See Email.
Write project actionsA sign-in action and a seed-data action save every tester time on every work item. See Project actions.
Add an agentStart with one from the catalogue, such as the Dependency Warden. See Setting up agents.
Choose how work startsIf opening a release would start more agent sessions than you want at once, set the project to start work manually. See Projects.
Add your customersSo that requests can be weighed at triage. See Customers.

Coming from another tracker#

Set the project’s next work item number above the highest number your old tracker used, so existing keys keep meaning what they meant.

If production is already on a version, set the project’s last released version, so Eido Build’s first release counts on from there.

Check the licence panel#

The top of Admin shows what this installation is licensed as, and when it last checked in. If it warns that it has not checked in, see Licensing.

Popular

Your first work itemRaise an enhancement and follow it through triage, the agent stages, approval and the merge.User guideHow a workflow runsThe stages a work item passes through, who has each one, and what each status means.User guideAcceptance criteria and QAWriting down what done means, testing a change against it with evidence, and deciding what happens to the bugs that turn up.User guideCutting a releaseFreezing a release, running its checks, deciding what to do about what they find, and shipping it.User guideOdieThe assistant on every page. It reads everything you can read, and anything it wants to change becomes a card for you to press.User guideCosts and budgetsWhat agents cost, where to see it, and the caps that stop a stage, an agent or a month from overspending.AdministrationIntegrations for agentsLetting agents act in other systems by granting them specific actions, without ever handing them a credential.AdministrationLicensingHow Eido Build checks its licence, what it sends when it does, and what to do if it locks.Install and licence