> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Autodesk API

> Invite users to your clients' Autodesk teams, assign and free product seats such as AutoCAD and Revit, and report seat use

The common uses are staff onboarding and offboarding, and seat reports: after the agent creates a new hire's Microsoft 365 account, it invites them to the client's Autodesk team and assigns their AutoCAD seat; when someone leaves, it frees their seats; on a schedule, it reports assigned against total seats for each client.

> [!NOTE]
>
> Automatically enabled when you configure Autodesk permissions in your agent workflow. On a ticket, the agent reaches only the Autodesk team mapped to the ticket's company on the Organization Mapping tab.

## What it does

* List the teams the connected account administers
* Find a user on a team by email, list a team's users, and see whose invitation is still pending
* Invite a user to a team
* Read each product pool's seats, assigned and total, and who holds each product
* Assign a product seat to a user, and free it

Autodesk's API cannot remove a user from a team, change a user's role, see or change groups, or change a seat that comes from a group or the whole team. The agent says so and gives the technician the steps in Autodesk Account.

## How the agent onboards a user

The agent looks the person up on the client's team first, and invites them when they are not there. It reads the team's product pools, picks the product the ticket names, and checks that the pool has a free seat. It then assigns the seat and reads the user's assignments to confirm. When the ticket names no product and more than one fits, it asks which.

## How the agent offboards a user

The agent reads the user's assignments and frees each seat assigned to them directly. It then tells the technician to remove the user from the team in Autodesk Account, or in the client's identity provider when the team syncs its directory, because the API cannot.

## Permission groups

| Group | Access levels | Covers |
| - | - | - |
| Teams | Disabled, Read Only | The teams the connected account administers, with their names and ids |
| Team Users | Disabled, Read Only, Read / Write | A team's users with their email, role and pending invitation; inviting a user |
| Product Seats | Disabled, Read Only, Read / Write | Product pools with seats assigned and total, who holds each product; assigning and freeing a seat |

## Access profiles

| Profile | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read | No write is allowed |
| **Helpdesk** | Every read | Every invitation and every seat change |
| **IT Admin** | Every read and write | Nothing; the API cannot grant an administrator role |
| **Full Automation** | Every supported call | Nothing |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.