---
title: "Access without teams"
description: "TIR projects sit directly under your account, and you manage access in each project; how team projects and roles carried over."
content_type: "concept"
product: "tir-iam"
platform: "TIR"
url: "/tir/tir-iam/concepts/access-without-teams/"
topic: ["users-and-access"]
---

# Access without teams

Projects sit directly under your account, and you manage their members, policies, and configuration in each
project's [project settings](/tir/tir-iam/how-to/manage-project-members-and-policies/).

## Projects that were in teams

- Projects that were grouped under a team now sit directly under the account, named
  `<Team Name>-<Project Name>`, for example "TeamAlpha-Billing Service". You can rename a project in its
  project settings.
- Projects from the Private Workspace are standard projects. Add or remove users in project settings. Every
  Admin has access to them, as with all projects.

For example, an account that had `project-private` in its Private Workspace and `project-A` in TeamA now shows
"PrivateWorkspace-project-private" and "TeamA-project-A" under the account.

## Roles after the change

- Team Lead became Project Manager on every project of that team.
- The Team Member role has been retired. A Project Lead stays Project Lead, and a Member stays Member, on the
  projects they were given.
- An Admin has access to every project, including those that were in the Private Workspace.

Apart from Admins, who now also reach the former Private Workspace projects, everyone kept the same
access, and only the role names changed. A user who managed TeamA's projects still reaches only
TeamA's.

| Role before the change                           | Before                                                                                                    | Now                                                                                          |
| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| Team Lead of TeamA                               | Ran every TeamA project: settings, members, and new projects in the team. Limited to TeamA.               | Project Manager on each former TeamA project, with the same control. Still limited to TeamA. |
| Team Member with Project Lead on a TeamA project | Ran that project and its settings. Creating and deleting projects was outside the role. Limited to TeamA. | Project Lead on the same project, unchanged.                                                 |
| Team Member with Member on a TeamA project       | Used that project's services only. Limited to TeamA.                                                      | Member on the same project, unchanged.                                                       |
| Admin                                            | Reached every team's projects, apart from the Private Workspace.                                          | Reaches every project, including those that were in the Private Workspace.                   |

What each role can do now is in [Roles and permissions](/tir/tir-iam/concepts/roles-and-permissions/).

## API addresses

API addresses have dropped the team part. Change the old form

```text
https://api.e2enetworks.com/myaccount/api/v1/gpu/teams/{team_id}/projects/{project_id}/{service_name}/
```

to

```text
https://api.e2enetworks.com/myaccount/api/v1/gpu/{service_name}/?project_id={project_id}
```

The older form will stop working after a transition period, and E2E will email you before that happens. The
updated [API reference](/api/tir/operations/post-notebooks/) shows the new form.