Projects enable teams to manage access to cloud databases through membership and permissions. Each account with cloud databases of InfoWorks ICM, InfoWorks WS Pro, InfoWater Pro, and InfoDrainage is structured with the following four layers:
- Team: The Team is where licensing is managed from manage.autodesk.com for all users within a customer account.
- Hub: A Hub is a deployment of Info360 cloud services within a selected Region. Only Team Admins can create Hubs. Members with Hub Admin Access can manage members of the Hub and create Projects.
- Project: Each Hub can contain many Projects, which are used to group together databases and manage the members that can access the data. Only Project Admins can access the Project Admin page to edit the list of Project Members.
- Database: Databases and their contents are managed from InfoWorks ICM, WS Pro and Info360 Model, which can be used to move databases from one Project to another.
For more information about Project Administration, go to the Administration Guide.
Role-based Permissions
For a user to access a cloud database in a Project, the user must be a member of the Project, and they must have an assigned Role of Model Editor or Model Reader. There is an exception where Admins of the Project are automatically treated with Model Editor permissions.
The table below outlines several potential permissions and access levels depending on varying configurations of licensing, Role, and Access Level.
User |
User 1 |
User 2 |
User 3 |
|||
---|---|---|---|---|---|---|
Licenses Assigned |
ICM, WS Pro |
ICM |
No license |
|||
Team A Projects |
Project 1 |
Project 2 |
Project 1 |
Project 2 |
Project 1 |
Project 2 |
Project Access Level |
Admin |
Admin |
Member |
Member |
Admin |
Member |
Project Role |
(ignored) |
(ignored) |
Editor |
Reader |
(ignored) |
Editor or Reader |
Access to Project Admin |
Yes |
Yes |
No |
No |
Yes |
No |
Access using Info360 Model |
Admin |
Admin |
Editor |
Read Only |
Admin |
Read Only |
Access using ICM |
Editor |
Editor |
Editor |
Read Only |
None |
None |
Access using ICM Viewer |
Viewer |
Viewer |
Viewer |
Read Only |
Read Only |
Read Only |
Access using WS Pro |
Editor |
Editor |
None |
None |
None |
None |
Access using WS Pro Viewer |
Viewer |
Viewer |
Viewer |
Read Only |
Read Only |
Read Only |
ICM versions 2026.1 and older |
Editor |
Editor |
Editor |
Read Only 2 |
None |
None |
ICM Viewer 2026.1 and older |
Viewer |
Viewer |
Viewer |
Read Only 2 |
None 1 |
None 1 |
WS Pro versions 2026.1 and older |
Editor |
Editor |
None |
None |
None |
None |
WS Pro Viewer 2026.1 and older |
Viewer |
Viewer |
Viewer |
Read Only 2 |
None 1 |
None 1 |
1 Desktop client versions 2026.1 and earlier require an Info360 Model entitlement, so no access is allowed without a license.
2 Desktop client versions 2026.1 and earlier do not support the Read-Only permissions enforced by the cloud. Attempts to edit forbidden objects will result in error messages.
The varying access levels for desktop clients are defined as the following:
- Editor: Full editing permissions to cloud databases, including running simulations.
- Read Only: The user can view all data as read-only. This allows copying and exporting of data, but no editing or simulations.
- None: Either no access to the software without a license, or no access to data in the Project if no Role is assigned.
- Viewer: This is a hybrid state based on legacy behavior of InfoWorks Viewers where some limited editing of data is allowed as defined on the WS Pro Free Viewer page.
The permissions for varying tasks within Info360 Model are outlined in the table below:
Task | Admin | Editor | Reader |
---|---|---|---|
Delete database |
Yes |
No |
No |
Restore database |
Yes |
No |
No |
Move database |
Yes* |
No |
No |
Cancel Run |
Yes |
Yes |
No |