Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Any referenced datasets can be downloaded from "Module downloads" in the module overview.
Transcript
00:06
Hi,
00:07
in this video we will learn about the admin
00:10
roles involved and an overview of the Vault permissions.
00:15
The Autodesk Vault server is a secure database.
00:19
A user must have an account
00:21
to access data and must be assigned appropriate user permissions.
00:26
Permissions are assigned based on rules.
00:29
When more than one rule is assigned,
00:31
the permission
00:33
is set.
00:34
as a union of the rules extending the permission of the user or group.
00:43
An Autodesk Vault administrator is tasked
00:45
with configuring and maintaining the Vault server
00:48
and client applications,
00:50
ensuring system stability through regular updates and performance management.
00:55
They manage user accounts,
00:57
assigned roles and permissions,
00:59
and oversee user access and security settings.
01:03
Administrators define and maintain the Vault fold structure,
01:07
set up project templates,
01:08
and manage file storage and replication.
01:12
They are responsible for configuring properties and metadata,
01:16
including setting up property definitions and
01:18
values to ensure organized metadata usage.
01:24
Document and data management duties include overseeing document lifecycles,
01:29
version control,
01:30
and check-in-checkout
01:31
processes.
01:33
Administrators implement and manage backup strategies,
01:37
perform regular database and file backups,
01:40
and handle data recovery in case of failures.
01:44
They ensure data security and compliance with organizational policies,
01:48
manage access control,
01:50
and monitor user activities and system access.
01:54
Additionally,
01:55
they provide technical support and training to Vault users,
01:59
educate them on functionalities
02:01
and best practices,
02:02
and create and maintain user documentation and guides.
02:06
This comprehensive rule ensures the efficient and
02:09
secure operation of the Autodesk Vault environment.
02:14
Autodesk Vault comes with 22 predefined roles,
02:18
including the admin role that we just discussed as shown on your screen.
02:23
Users or groups can be assigned with any of these
02:27
roles as per the permissions required by a role.
02:31
Administrators can copy any existing role to create a new custom role definition
02:36
to add or modify permissions,
02:39
or they can create a new role definition
02:42
from scratch using the new role option in the roles management.
02:48
Now,
02:48
let's see how rules can be applied to a user group.
02:54
Log in to Vault as an administrator.
02:57
Click on tools administration,
03:00
Global settings,
03:03
to access the global settings dialogue.
03:08
If you click on manage roles,
03:10
that is where you will be able to
03:13
access the role definitions,
03:15
create new role definitions,
03:17
or
03:18
delete any custom role definitions.
03:22
Any rule definition can be understood by double clicking on it
03:25
and all the permissions given
03:28
can be seen.
03:31
You can add or remove
03:33
additional permissions
03:35
if it is a custom role,
03:38
but any
03:39
system definitions
03:41
cannot be edited.
03:50
Now let's create a user group involved
03:53
and assign
03:54
one of these roles
03:56
for that user group.
04:03
To create a user group,
04:04
click on Tools,
04:06
Administration,
04:08
global settings.
04:10
in the global settings dialogue,
04:12
click on managed access.
04:15
You can click on Groups tab to access the groups,
04:18
and click on Users to see the users.
04:23
Let's click on Groups tab here
04:25
and click on New.
04:30
I will specify
04:31
the
04:32
Group name as
04:35
Designers.
04:38
You can provide any email alias if any email alias exists.
04:47
Click on the roles to define
04:49
the appropriate roles for this group.
04:54
You can choose
04:56
Document editor
04:58
(Level 1)
04:59
and Document Manager (Level 1) permission.
05:04
It should suffice for the designers.
05:08
Click on Vaults... to provide access to this group
05:12
for any Vault database that exists on this server.
05:16
We will use the existing Vault database
05:18
that is Vault,
05:20
and click OK.
05:23
You can add any other groups here.
05:26
Or you can define group managers as well.
05:33
You can disable the group by unchecking the checkbox here.
05:37
Now let's add the users.
05:47
Any users assigned to this group will have access as per the
05:50
permissions specified by adding the group on any objects or lifecycles.
05:57
Click OK and close
05:59
to exit the dialogue.
06:02
Object-based permissions can be specified by using this group.
06:07
If you wish to add folder level security,
06:11
select a folder,
06:12
click on details,
06:15
and click on the security tab.
06:18
Click the add user icon.
06:21
Filter groups,
06:24
and add the group here, and click OK.
06:28
Specify the permission that is allowed for this group.
06:31
Either specify Allow or leave it blank.
06:34
Though deny is available,
06:35
it is not recommended to use deny unless you really want to harden the security.
06:40
Leaving it as blank should be enough to restrict a user to not have permissions.
06:47
We will allow the designers to modify the folder
06:50
contents and allow them to download the folder contents.
06:53
We will restrict them from deleting the files.
06:56
Let's click OK and use propagate
06:59
on the changes.
07:05
You can see that
07:06
the logged in user here is administrator,
07:09
and since
07:10
the administrator is not part of the
07:13
designer's group that we just created,
07:15
the administrator now cannot modify the files here.
07:18
This is how users and groups can be used to apply object-based permissions in Vault.
07:23
Groups can also be used to configure permissions using Vault lifecycles.
07:34
Let me undo
07:36
the change we just did.
07:43
OK.
07:46
Now you can see the administrator has regained the access because
07:50
there is no restrictions applied as part of object-based security.
07:55
Now let's go ahead and configure
07:57
lifecycle with this user group.
08:07
We will edit the inventory release process.
08:13
For WIP state I'll add
08:17
the designer's group
08:21
and remove the
08:23
others from the permission list.
08:28
The designers who will be having access in the work in progress state.
08:32
Apply this change and click OK.
08:38
You can see that for the files that are in work in progress state,
08:42
permissions are now applied
08:44
based on the security configuration
08:46
that we just applied using the designers.
08:50
The administrator is not part of the designer's group and hence has no access
08:55
in the work in progress state.
08:56
You can configure the access for administrator either
08:59
by adding the administrator to the designers group
09:02
or adding the administrator user directly to the WIP state security.
09:08
This is how Vault permissions can be
09:10
configured using user groups and role permissions.
Video transcript
00:06
Hi,
00:07
in this video we will learn about the admin
00:10
roles involved and an overview of the Vault permissions.
00:15
The Autodesk Vault server is a secure database.
00:19
A user must have an account
00:21
to access data and must be assigned appropriate user permissions.
00:26
Permissions are assigned based on rules.
00:29
When more than one rule is assigned,
00:31
the permission
00:33
is set.
00:34
as a union of the rules extending the permission of the user or group.
00:43
An Autodesk Vault administrator is tasked
00:45
with configuring and maintaining the Vault server
00:48
and client applications,
00:50
ensuring system stability through regular updates and performance management.
00:55
They manage user accounts,
00:57
assigned roles and permissions,
00:59
and oversee user access and security settings.
01:03
Administrators define and maintain the Vault fold structure,
01:07
set up project templates,
01:08
and manage file storage and replication.
01:12
They are responsible for configuring properties and metadata,
01:16
including setting up property definitions and
01:18
values to ensure organized metadata usage.
01:24
Document and data management duties include overseeing document lifecycles,
01:29
version control,
01:30
and check-in-checkout
01:31
processes.
01:33
Administrators implement and manage backup strategies,
01:37
perform regular database and file backups,
01:40
and handle data recovery in case of failures.
01:44
They ensure data security and compliance with organizational policies,
01:48
manage access control,
01:50
and monitor user activities and system access.
01:54
Additionally,
01:55
they provide technical support and training to Vault users,
01:59
educate them on functionalities
02:01
and best practices,
02:02
and create and maintain user documentation and guides.
02:06
This comprehensive rule ensures the efficient and
02:09
secure operation of the Autodesk Vault environment.
02:14
Autodesk Vault comes with 22 predefined roles,
02:18
including the admin role that we just discussed as shown on your screen.
02:23
Users or groups can be assigned with any of these
02:27
roles as per the permissions required by a role.
02:31
Administrators can copy any existing role to create a new custom role definition
02:36
to add or modify permissions,
02:39
or they can create a new role definition
02:42
from scratch using the new role option in the roles management.
02:48
Now,
02:48
let's see how rules can be applied to a user group.
02:54
Log in to Vault as an administrator.
02:57
Click on tools administration,
03:00
Global settings,
03:03
to access the global settings dialogue.
03:08
If you click on manage roles,
03:10
that is where you will be able to
03:13
access the role definitions,
03:15
create new role definitions,
03:17
or
03:18
delete any custom role definitions.
03:22
Any rule definition can be understood by double clicking on it
03:25
and all the permissions given
03:28
can be seen.
03:31
You can add or remove
03:33
additional permissions
03:35
if it is a custom role,
03:38
but any
03:39
system definitions
03:41
cannot be edited.
03:50
Now let's create a user group involved
03:53
and assign
03:54
one of these roles
03:56
for that user group.
04:03
To create a user group,
04:04
click on Tools,
04:06
Administration,
04:08
global settings.
04:10
in the global settings dialogue,
04:12
click on managed access.
04:15
You can click on Groups tab to access the groups,
04:18
and click on Users to see the users.
04:23
Let's click on Groups tab here
04:25
and click on New.
04:30
I will specify
04:31
the
04:32
Group name as
04:35
Designers.
04:38
You can provide any email alias if any email alias exists.
04:47
Click on the roles to define
04:49
the appropriate roles for this group.
04:54
You can choose
04:56
Document editor
04:58
(Level 1)
04:59
and Document Manager (Level 1) permission.
05:04
It should suffice for the designers.
05:08
Click on Vaults... to provide access to this group
05:12
for any Vault database that exists on this server.
05:16
We will use the existing Vault database
05:18
that is Vault,
05:20
and click OK.
05:23
You can add any other groups here.
05:26
Or you can define group managers as well.
05:33
You can disable the group by unchecking the checkbox here.
05:37
Now let's add the users.
05:47
Any users assigned to this group will have access as per the
05:50
permissions specified by adding the group on any objects or lifecycles.
05:57
Click OK and close
05:59
to exit the dialogue.
06:02
Object-based permissions can be specified by using this group.
06:07
If you wish to add folder level security,
06:11
select a folder,
06:12
click on details,
06:15
and click on the security tab.
06:18
Click the add user icon.
06:21
Filter groups,
06:24
and add the group here, and click OK.
06:28
Specify the permission that is allowed for this group.
06:31
Either specify Allow or leave it blank.
06:34
Though deny is available,
06:35
it is not recommended to use deny unless you really want to harden the security.
06:40
Leaving it as blank should be enough to restrict a user to not have permissions.
06:47
We will allow the designers to modify the folder
06:50
contents and allow them to download the folder contents.
06:53
We will restrict them from deleting the files.
06:56
Let's click OK and use propagate
06:59
on the changes.
07:05
You can see that
07:06
the logged in user here is administrator,
07:09
and since
07:10
the administrator is not part of the
07:13
designer's group that we just created,
07:15
the administrator now cannot modify the files here.
07:18
This is how users and groups can be used to apply object-based permissions in Vault.
07:23
Groups can also be used to configure permissions using Vault lifecycles.
07:34
Let me undo
07:36
the change we just did.
07:43
OK.
07:46
Now you can see the administrator has regained the access because
07:50
there is no restrictions applied as part of object-based security.
07:55
Now let's go ahead and configure
07:57
lifecycle with this user group.
08:07
We will edit the inventory release process.
08:13
For WIP state I'll add
08:17
the designer's group
08:21
and remove the
08:23
others from the permission list.
08:28
The designers who will be having access in the work in progress state.
08:32
Apply this change and click OK.
08:38
You can see that for the files that are in work in progress state,
08:42
permissions are now applied
08:44
based on the security configuration
08:46
that we just applied using the designers.
08:50
The administrator is not part of the designer's group and hence has no access
08:55
in the work in progress state.
08:56
You can configure the access for administrator either
08:59
by adding the administrator to the designers group
09:02
or adding the administrator user directly to the WIP state security.
09:08
This is how Vault permissions can be
09:10
configured using user groups and role permissions.
For an overview of available roles, or to create, edit, copy, or delete roles, open the Role Management dialog box.
Create a new user group. You can name the group, enter the email distribution addresses for the group, assign roles to the group, and identify which vaults the group can access.
Note: You must be assigned the role of Administrator to perform this operation.
How to buy
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © 2025 Autodesk Inc. All rights reserved
Sign in to start learning
Sign in for unlimited free access to all learning content.Save your progress
Take assessments
Receive personalized recommendations
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement. May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.