1. Organize Projects and Roles
Autoheal has two levels. The organization is your company's Autoheal account. A project holds the work of one team. On this page, you make a practice project for new people, give a teammate a role, and check the roles that you have.
What is in the organization and what is in a project
| Level | What it holds | Who manages it |
|---|---|---|
| Organization | Users, user groups, organization service accounts, sign-in and SSO, the list of projects, roles, and Insights for all projects | Org Admin |
| Project | Agents, skills, triggers, runs, artifacts, Integration Connections, the Context Graph and memories, agent policies, secrets, the audit trail, and project service accounts | Project Admin |
The work stays in its project. An agent in one project cannot see the agents, runs or Integration Connections of another project. To use one Integration Connection in more than one project, share it (see page 3).
To open the organization, click the project switcher at the top of the sidebar and select your organization. Its Settings has IAM, Users, User groups, Service accounts, Authentication, Integrations and Roles. A project's Settings has three groups: GENERAL, PLATFORM and ACCESS.
The four roles
| Role | Given on | Can do |
|---|---|---|
| Read-only | Organization or project | See agents, runs, artifacts, settings and the audit trail. Cannot change anything, and cannot approve a tool call. |
| Member | Project | Create, change and run agents and skills. Create and change triggers. Answer an agent's questions and approve its tool calls. Save secrets. Cannot delete agents, triggers or artifacts, connect integrations, change agent policies or give access. |
| Project Admin | Organization or project | Everything in the project, also Integration Connections, agent policies, sharing, service accounts and access. |
| Org Admin | Organization | Users, user groups, projects, sign-in and organization service accounts. Holds no project content except secrets: an Org Admin who works in a project also needs a role there. |
A role given on the organization applies in every project. Roles only add access. A role on a project never takes away access that the organization gives.
Step 1: Make a practice project
Autoheal has no built-in practice project. You make one, and new people use it before they get access to production projects. In the practice project, they do Build Your First Agent, make mistakes, and delete what they made.
- Open the organization
You must be an Org Admin. Click the project switcher and select your organization. The Projects page opens.
- Create the project
Click New project. In Name, type
Practice. In Description, typeWhere new people learn Autoheal. Click Create project.
You become the Project Admin of the new project. The project is empty: it has no agents, no Integration Connections and no members.
Step 2: Give a teammate access
Give a new teammate the Member role on the practice project, and the Read-only role on the production project of their team. When they are ready, change Read-only to Member.
- Open IAM
Open the practice project. Go to Settings → ACCESS → IAM, and click Grant access.
- Pick the person and the role
In Principals, find the person or a user group by name or email. In Roles, keep Member. Click Save.
- Do the same for the production project
Open the production project, and do the same steps with the Read-only role.
You can also give roles from the organization's IAM. There, the Role binding section has a Where field: the organization, or one project. Select one project. A role on the organization applies in every project.
People who sign in through SSO for the first time get the Member role on the Default Project. If your production work is in the Default Project, change the Default role in the organization's Authentication settings. See Single Sign-On.
Step 3: Check your roles
Click the project switcher. Check that the list shows the Practice project. Open the practice project, go to Settings → ACCESS → IAM, and check that your row shows Project Admin.
I want to ... go to ...
| I want to | Go to | Role |
|---|---|---|
| Make a project | Organization → Projects → New project | Org Admin |
| Give someone a role on one project | Project → Settings → ACCESS → IAM → Grant access | Project Admin |
| Give a role in every project | Organization → Settings → IAM → Grant access | Org Admin |
| Invite a new person | Organization → Settings → Users → Invite users | Org Admin |
| Make a team group | Organization → Settings → User groups → New user group | Org Admin |
| Set up SSO | Organization → Settings → Authentication | Org Admin |
| See what each role can do | Organization → Settings → Roles | Read-only on the organization |
| Connect GitHub, Slack or another system | Project → Settings → GENERAL → Integrations | Project Admin |
| Make a person approve tool calls | Project → Settings → PLATFORM → Agent policies | Project Admin |
| Save a token for agents | Project → Settings → PLATFORM → Secrets | Member |
| See every tool call of every agent | Project → Settings → PLATFORM → Audit trail | Read-only |
| Use an Integration Connection from another project | Project → Settings → ACCESS → Shared resources | Project Admin |
What to know
- One team, one project. A second team with its own agents, Integration Connections and people gets its own project.
- The app has no way to delete a project. Choose project names with care.
- Any Member can commit to
mainin a project. Use branches to try changes (see chapter 6), and give Member on production projects only to people who can change production agents. - Each project's audit trail shows the arguments and output of every tool call. A Read-only role on a project lets a person read them.
- When an Org Admin gives themselves a role on a project, Autoheal records it and sends an email to the other admins.
From the CLI
autoheal project create "Practice" --id practice --no-use
autoheal project list
The first command makes the project. Only an Org Admin can run it. --no-use keeps the CLI in your current project. The second command lists the projects that you can open and your roles in each. Roles show as IDs, for example project_admin and org_admin.
The CLI cannot give roles. Use IAM in the web app.
See Roles & Permissions for every permission, and Managing Access for users, user groups and IAM.