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:00
[MUSIC PLAYING]
00:11
BRYSON ANDERSON: Autodesk Accelerators
00:12
are designed to help your team stay ahead
00:14
of the curve with the latest workflows.
00:16
These include on-demand courses, prerecorded coaching,
00:19
as well as live coaching.
00:20
To see the full list of topics, visit the Customer Success Hub.
00:25
Take a moment to read over the safe harbor statement.
00:28
This is a reminder that we may make statements
00:29
about future developments, these are not
00:31
intended to be a guarantee but reflect
00:33
our current expectations and assumptions.
00:38
Before we get started, let me introduce myself.
00:40
My name is Bryson Anderson.
00:41
I'm based out of Utah, been in the IT industry
00:44
for about 14 years now, the last 10 years
00:46
in the AEC Marketplace working with firms
00:49
in all aspects of their IT, including
00:51
data management and collaboration
00:52
for Autodesk workflows.
00:55
Welcome to the Autodesk Accelerator,
00:57
set folder structures and permissions in Autodesk Docs.
00:60
The learning objectives for the session
01:02
is to understand how to create an organized folder structure,
01:04
understand how to assign permission
01:06
and access to folders, learn how to accept invitations
01:09
to Autodesk Docs.
01:11
The workflow we're going to follow
01:12
is accept project admin invite from the account admin,
01:15
create an organized folder structure,
01:17
invite and assign users access to directories,
01:20
assign permission levels, accept user invite from the project
01:23
admin, and subscribe to folders for email notifications.
01:28
So let's start with our first step,
01:30
creating an organized folder structure.
01:32
This is going to be the first step in our workflow.
01:35
When setting up a project, one of the first things
01:37
we need to do is create a folder structure.
01:39
You probably already have a project folder structure
01:41
and that's a really good place to start from.
01:43
A couple of things you want to keep in mind as you're
01:44
setting up a BIM 360 project.
01:46
You want to lay out folders to support your workflow
01:48
for collaborating with other companies,
01:50
so whether that means creating folders for companies
01:52
or folders for disciplines.
01:55
And keep permissions in mind.
01:56
Your folder structure should allow
01:57
you to set access permissions to meet your project requirements.
01:60
So, for example, if you've got subconsultants
02:02
that should only have read to some folders
02:04
and write to others.
02:06
You'll want to subfolder those correctly
02:07
so that you can set those permissions.
02:09
There are a couple of ways to create folder structures.
02:11
The first way is to manually create the folder
02:13
structure in Autodesk Docs.
02:15
On the Files tab, you'll have two default locations
02:18
for the field and project files.
02:20
To create a subfolder underneath either of those--
02:22
if you hover over them, you'll see these three dots here,
02:25
this ellipsis.
02:25
When you hover over that and click,
02:27
you'll have some options.
02:29
One of those is to add a subfolder.
02:31
When you click Add Subfolder, a subfolder is created.
02:34
You can then change the name and hit the checkbox
02:36
to finish and then keep going down through,
02:38
adding subfolders and additional folders as needed.
02:41
All of the options for adding folders, renaming them,
02:44
deleting them can all be found by hovering over the folder,
02:47
clicking on the ellipsis, and then picking,
02:49
rename, add subfolder, whatever is that you want to do.
02:52
Now, if you have a large folder structure
02:54
or you have a folder structure that already exists,
02:56
maybe you've got it on your local server
02:57
already, another way that you can
02:59
add these is by actually uploading
03:01
the folders through the Autodesk Desktop Connector.
03:03
The Desktop Connector is an application
03:05
that you install on your computer
03:06
and it connects the Autodesk Docs to your Windows File
03:09
Explorer so that you can easily copy things
03:12
from one location to the other.
03:13
If you've already created an existing folder structure,
03:15
all you've got to do is just drag and drop it
03:17
from your local location over to the project files location.
03:20
As you're doing this, you'll want
03:21
to either drag and drop or do a Control-C, Control-V shortcut
03:25
for copy and paste.
03:26
Because when you right click in the Desktop Connector folder,
03:29
you don't get the same menu that you get inside of Windows.
03:31
There's not a paste.
03:33
So when you copy it out of File Explorer,
03:36
in order to paste it into the Desktop Connector,
03:39
either drag and drop it or use Control-V, the keyboard
03:42
shortcut, for pasting.
03:43
Once you've got that folder structure moved over
03:45
to the Desktop Connector location,
03:47
you can add more folders through here
03:49
or through the web browser.
03:51
You can do it either way.
03:52
Now that we have a folder structure,
03:54
we can move on to the next step--
03:55
to set intuitive organized permissions.
03:59
This is going to be our second step in the workflow.
04:01
A couple of things to consider when
04:02
you're looking at permissioning out your folders.
04:04
Project admins have full access to every file in every folder.
04:08
As a project admin they're unrestricted,
04:09
you cannot restrict them.
04:11
So keep your project admins more to a minimum,
04:13
realizing that they have full access to everything.
04:16
Permissions are also set by folder and subfolder.
04:19
They're not set by the individual file.
04:21
When you set permissions on a folder,
04:23
all of the folders underneath it will inherit the permissions
04:26
that you set on that parent folder.
04:27
You can then drill down and change subfolder permissions
04:30
as you need.
04:31
Permissions can be set by either individual users, companies,
04:35
or roles.
04:36
You can use one or a mix of all the types.
04:38
But when you get into using lots of companies, and users,
04:41
and roles, it can get a little bit confusing about where
04:44
permissions are coming from.
04:45
If you've got a person added by a company, and by a role,
04:48
and by the individual user, it can get a little bit messy
04:50
when you're trying to figure out why someone does or does not
04:52
have permissions.
04:53
I try to keep my permissions as simple as possible,
04:55
using things like company and roles
04:58
as groups to add permissions and only adding users individually
05:01
when I really need to.
05:02
You'll also want to think about software-specific workflows
05:05
and permissions required.
05:06
So, for example, Revit Cloud Worksharing in BIM Collaborate
05:09
Pro.
05:09
Users are going to need view and download to link a Revit model.
05:12
So you'll want to kind of think all these things through
05:14
as you're getting your folder structure set up and getting
05:16
things permissioned out.
05:17
Permissions are set in Autodesk Docs
05:19
on the Files tab, same place where we created subfolders.
05:23
If you click those ellipsis, one of the options is permissions.
05:26
If you click on Permissions, it will pop out
05:28
the permissions window and you can start
05:30
setting those permissions.
05:31
You can use the companies and roles,
05:33
like we talked about earlier, to create groups to make things
05:35
easier and more scalable so that down the road, if you
05:38
add a company with permissions to a folder
05:40
and then you invite someone else from that company,
05:42
you don't have to come in and remember to add them
05:44
individually to permissions.
05:45
They'll inherit permissions based on that company or role
05:47
that they're assigned to.
05:49
One thing to keep in mind is that the highest access
05:51
granted wins.
05:52
So, for example, if you had company settings at view
05:55
but you invited the individual user
05:56
and gave them higher permissions,
05:58
they would have those higher permissions.
06:00
There are four categories of permissions-- view,
06:02
create, edit, and manage.
06:05
And there's different levels within those categories.
06:07
If you have no permission set at all,
06:09
then the user can't see the folder.
06:11
To add someone, click the Add button and type
06:14
in the either username, the company, or the role.
06:17
And then you'll use this dropdown
06:19
to select what permission level you want to give them.
06:21
So, for example, under view we have view only,
06:23
and view+download.
06:24
And similarly, in create, one level
06:27
does not have permissions to upload while the other does.
06:29
So select the permission level that you want
06:31
and then continue on adding permissions.
06:34
Let's jump into the demo video on setting up
06:36
folders and permissions.
06:38
Creating an organized folder structure
06:39
is key to project setup.
06:41
You'll want to lay out your folders
06:42
to support your workflows, including collaborating
06:44
with other companies.
06:46
Your current project folder structure
06:47
is probably a really great place to start from.
06:49
You likely already have a folder structure
06:51
that you use on projects.
06:53
Starting with that gives you a really good base
06:56
and you can build on it from there.
06:58
As you begin setting up your project folder structure,
07:00
one key thing to consider is who's
07:02
going to be involved in this project.
07:04
Is it just an internal project or they'll
07:06
be outside consultants involved?
07:08
That will help dictate what kind of folder structure you set up.
07:11
To do this, we're going to use the Autodesk Desktop Connector.
07:14
The Desktop Connector is a utility
07:15
that connects the Autodesk Docs folders with your Windows File
07:20
Explorer.
07:20
So we're looking at that here.
07:22
On the right hand side, I'm browsed into my Desktop
07:25
Connector location.
07:26
On the left hand side, I have a local folder template.
07:29
These are just empty folders that I can copy and paste
07:33
from my local directory over into Desktop Connector, which
07:37
will then upload them into Autodesk Docs.
07:40
Now one thing to note as you're doing
07:41
this is when you right click in Windows File Explorer,
07:44
you get all kinds of options, including copy and paste.
07:47
When you right click in Desktop Connector
07:49
you have the option to create a new folder,
07:50
but your right click context menu is different.
07:53
So to copy and paste over, you need to either highlight, drag
07:56
and drop, or use your shortcut keys Control-A
08:00
to select all, Control-C to copy, Control-V to paste.
08:04
I like to just select and drag and drop.
08:07
And you'll notice down here the Desktop Connector is
08:10
going to tell us that it's transferring
08:12
those folders over.
08:13
It's creating that folder structure on the cloud,
08:15
much easier than creating them manually one by one.
08:18
We can use what we already have in Windows Explorer
08:20
or just create in Windows File Explorer
08:23
a directory and then copy and paste it over.
08:26
Jumping back over to Autodesk Docs,
08:28
I copy those into a folder called Files.
08:31
And you'll see that folder structure created here.
08:34
I can then modify that here in Autodesk Docs or I
08:37
can go back to my Desktop Connector location
08:39
here and modify file names or folder names by doing a rename,
08:44
add new folders, copy and paste other folders over,
08:48
however I want to do that.
08:49
Once I've got my folder structure created,
08:51
I need to think about permissions.
08:53
So if I hover over any of these folders
08:55
and click these three dots, I can then go to Permissions.
08:60
So items are permissioned by folder
09:03
and not by file in Autodesk Docs.
09:05
So I'm going to actually set folder permissions
09:07
that wherever files exist within that folder
09:09
are dictated by the folder permissions.
09:11
I can assign out permissions by either individual users,
09:14
by companies, or by roles.
09:16
I also have four different categories
09:19
of permission types--
09:20
view permissions, create permissions, edit permissions,
09:24
and manage permissions.
09:26
Under view and create, you'll notice I
09:27
have a couple different types--
09:29
view only or view and download.
09:30
And then on the create type whether or not I
09:32
want people to be able to upload or not.
09:34
So I've got all kinds of permission settings that I
09:36
can permission based on these users or group types,
09:39
if you will, companies, and roles.
09:41
Typically, I like to permission things
09:42
out as much as I can using companies, roles
09:45
as kind of secondary grouping, and then
09:48
adding users one by one if I really need to.
09:50
But adding by companies makes my permissions really modular.
09:53
So, in the future, if I have, say,
09:56
MEP Company added here a few permissions
09:58
and I add somebody to the MEP Company,
10:01
I don't have to remember to go give them folder permissions.
10:03
They're going to have folder permissions already set
10:05
by their company.
10:07
This really helps with scalability
10:08
so that as you add and remove people from projects,
10:11
add and move them from companies or roles,
10:13
permissions to folders are automatically handled.
10:15
Now, you'll notice a couple of things in here.
10:17
First of all, on this user, it tells me it's a project admin
10:21
and they remove button is not there.
10:23
So any project administrator will have full access
10:26
to all folders within the project
10:29
that they are a project admin for.
10:31
It's not something that you can configure or lessen
10:33
their permissions.
10:34
That's just how this works.
10:36
Built into the system is all project
10:38
administrators have default access to everything.
10:41
So you'll want to make sure that you keep your project
10:43
administrators to a minimum so you're not
10:45
leaving every folder wide open to everybody.
10:47
In this scenario, this is the architectural folder.
10:50
So I gave the architectural company edit permissions.
10:52
I gave the Structural and MEP company view permissions.
10:56
I've got full permissions because I'm
10:58
a project administrator.
10:59
And then I gave Shawn manage.
11:01
So the manage permission level gives them
11:04
the ability that can change folder permissions
11:06
on their folder.
11:07
So if they're not an administrator,
11:09
but I want them to be able to manage
11:10
who has access to their folder and change that,
11:13
I can give them manage permissions.
11:14
They then have full edit permissions as well as
11:17
the ability to manage who has access to the folder.
11:21
Adding additional permissions is easy.
11:23
You click the Add button, put in the name--
11:25
either by their name or by their email
11:27
address-- the role, or the company.
11:29
So I could select the role of project engineer
11:33
and give that a permission level.
11:35
We'll say we want project engineers
11:37
to have view and download.
11:41
Click Add and we'll add them here to the list.
11:43
If I need to remove permissions, I can simply just click Remove.
11:47
As I add permissions to folders, you'll
11:50
notice subfolders underneath are going
11:52
to inherit those permissions.
11:53
So if I click on this Consumed folder, or the Dynamo,
11:56
or FormIt folders underneath architecture.
11:59
You'll notice that it's saying inherited.
12:02
It's not given the ability to remove that permission level.
12:07
I can, however, give them more permissions on a subfolder.
12:11
So, for example, under MEP Company, who has view,
12:14
I could give them create, edit, or manage on this folder.
12:17
I cannot go backwards.
12:18
Notice view only as grayed out.
12:20
If I go to Shawn here, who has manage,
12:23
you'll notice I can't change anything.
12:25
So I can add additional permissions to subfolders,
12:28
but I can't restrict to a lower permission level on subfolders.
12:32
So keep that in mind as you lay out folders,
12:35
understanding that subfolders of that folder--
12:38
you can add additional permissions to the subfolders,
12:41
but you can't restrict to a lower permission level.
12:45
Let's also talk about permission levels
12:46
in the For the Field folder.
12:49
So For the Field folder is a specialized folder that
12:52
has a specialized workflow.
12:53
Anything put in For the Field is synced to mobile devices.
12:57
Some of the other Autodesk Construction Cloud applications
12:59
like plan grid and build have specialized workflows
13:02
for this folder.
13:03
Keep in mind also that BIM Collaborate Pro
13:05
tools, like Revit Cloud Worksharing
13:07
and the collaboration for Civil 3D and Plant 3D,
13:10
requires that files be in project files.
13:12
If you put them in For the Field,
13:14
they're not accessible through those applications.
13:16
So when you add things to For the Field,
13:17
just be sure you know what the use case is
13:20
for it being in For the Field.
13:22
It's basically a place for a virtualized document plan set
13:25
to have in the field is stored.
13:27
But permissions are a little bit different For the Field area.
13:30
So let's go ahead and click on For the Field.
13:32
We've got one PDF file in here.
13:35
So let's click on the permissions.
13:39
You'll notice we have an everyone in here
13:42
and it's not removable.
13:44
And if we go to the permissions, we
13:46
can't give it anything higher than view or view and download.
13:49
Those are our two options.
13:51
Does everyone have view only or view and download?
13:53
We can't change anything else on the everyone category here.
13:57
That is by design from For the Field.
13:59
It even gives you the little message
14:01
here across the top that files in this folder
14:03
are available to all project members and their synced
14:05
to mobile devices.
14:06
So keep in mind--
14:08
anything you put in For the Field everybody
14:10
has view access to.
14:12
Now, you can give others higher access than that.
14:15
So we could come in here and we could say let's give Shawn
14:20
some higher permissions.
14:21
We'll give him edit permissions.
14:25
And now Shawn has edit permissions on this folder.
14:28
So one thing to note with adding people
14:31
by group and by individual name here--
14:33
so both Shawn and I are going to be part of the everyone group,
14:36
but we're also added individually here as users.
14:39
So whatever the highest permission
14:40
level given to the user is is what will win.
14:43
So, in this case, the group permission is giving it view.
14:47
But Shawn's got edit permissions through user base
14:49
permissioning, so he'll have edit on this folder.
14:52
You'll want to go through, set up your permissions
14:54
in For the Field, set them up in project files,
14:56
get that structure just the way you want it for your project,
14:59
and then it's time to go start adding members.
15:02
Next, we're going to look at inviting users
15:04
to Autodesk Docs.
15:07
This is going to be the third step in our workflow.
15:10
Any user that needs access to Autodesk Docs
15:12
needs to be invited to the project by a project admin.
15:14
Admins can invite members from the Members tab in Docs
15:17
or from the project admin console.
15:19
When adding members, you can add them one by one
15:21
or you can upload them through a list.
15:25
So if you have an existing list of members
15:26
that need to be added, instead of typing them one by one,
15:29
you can upload that list and add them.
15:30
When you add members, you need to specify
15:32
the company, the role, and whether or not
15:34
they're going to have admin rights,
15:36
as well as give them product access required
15:38
for their access needs to Autodesk Docs.
15:40
Once you have that configured, you can click Add
15:43
and it will send them a welcome email.
15:47
You can view your existing users on the Members tab in project
15:50
admin or in Autodesk Docs.
15:51
And you can change any of the settings
15:53
that you want-- the company, the role, their access
15:55
level, their assigned products.
15:57
Those can be edited by a project admin any time.
16:01
As I mentioned earlier, all members
16:03
are going to get a welcome email.
16:04
Each invited user will receive a welcome email like you see here
16:07
on the right hand side.
16:08
Depending on if the user has been
16:10
added to a project on your account before or not,
16:12
this little blue button down here at the bottom
16:14
may read differently.
16:15
On this one, this user invited had not been added to a project
16:18
before and so they need to click Activate Membership to finish
16:21
joining that project.
16:23
Otherwise, it would say join the project or something similar.
16:27
Let's jump into the demonstration
16:28
on adding members.
16:30
Now that we've got a folder structure and permissions
16:32
in place, let's start adding some members.
16:34
Adding someone is very simple.
16:36
We just click the Add Members button here
16:38
on the Members tab of Docs.
16:40
We could also go to the project admin
16:43
and go to the Members tab of project admin.
16:46
It's going to give us the same thing in either place.
16:48
In order to add members to a project,
16:50
you do need to be a project admin.
16:52
So if you are in the Docs here and you go to members
16:57
and you are not in admin, you'll won't have an Add Members
16:60
button here.
17:00
You will see the list of members on the project,
17:03
but you will not be able to add members to the project.
17:06
I am a project admin, so I do see the Add Members.
17:09
I'll go ahead and click that.
17:11
So to add somebody, we just need to enter their email address.
17:14
If the person we're adding is already
17:16
a member of our account, so they've
17:18
been added to another project, the account actually
17:21
creates a directory of people that
17:23
have been involved in projects on that directory before.
17:27
So when we go to start typing, for example, you'll notice here
17:30
is me, I'm already in the project.
17:33
Here's somebody else, who's been added to another project,
17:36
so they're already in our project directory,
17:38
so we could just select them.
17:40
If we haven't added them to any project on our account
17:43
in the past, we'll just type in their email address, hit Enter,
17:47
and we'll get to the same thing here.
17:49
So we will add this user.
17:51
The next thing to do is assign them to a company.
17:53
So if you remember, as we are setting up our permissions,
17:56
we set up a lot of permissions based on company.
17:58
So adding someone to a company here is going to do two things.
18:01
One, organize them into that company
18:03
but also give them folder permissions based
18:06
on that company we set.
18:07
So let's go ahead and add him to the Structural Company.
18:11
Now, the same thing goes for roles.
18:12
We've got a whole bunch of roles here.
18:14
These are all the default roles.
18:15
You can-- project administrators can configure their own roles.
18:19
So if you want to set a custom set of roles, you can do that.
18:21
We'll select something here.
18:24
How about we say he is an engineer.
18:25
If we have folder permissions based on roles,
18:28
that will also give him permissions based on that.
18:31
Then we need to select whether they are a project member
18:33
or a project administrator.
18:35
Keep in mind that administrator has full access to everything,
18:38
so keep those to a minimum.
18:40
We'll set this one as a project member.
18:42
The last thing that we need to do here
18:44
is assign them to products.
18:46
So we need to give them at least Docs.
18:49
Docs is that base location where everything is stored.
18:52
So to do anything, they need to have that Docs platform.
18:56
We also can assign any other modules, so
18:58
the Design Collaboration module, Model Coordination.
19:01
We'll leave this one at just Docs.
19:03
And we click Add.
19:05
This message will tell us that it's adding members
19:07
and then it might take just a moment to do that.
19:09
After a couple of seconds, we'll see that user here in the list,
19:12
that they were added moments ago.
19:13
That user is also going to get a welcome email
19:16
like this, says welcome to the project with a link
19:19
to the project.
19:20
This message is a little bit different for this user
19:22
because this user was already added to the account.
19:24
If they were not added to our account,
19:26
this button would look a little bit different.
19:27
It would have had an activate your membership
19:29
or other message here telling them
19:31
they need to join the project.
19:32
They click that link to join the project,
19:35
they're now added to the account and have
19:36
access to that project.
19:39
Once they log into Docs and go to the Files section,
19:43
they'll be able to see any folders
19:45
and files in those folders that they've been given access to.
19:50
Jumping into our final topic, create project templates.
19:53
Again, this is going to be the final step in our workflow.
19:57
One of the things we can do to simplify and speed up
19:59
our project creation in the future is to create templates.
20:02
Templates can contain folders and permissions, members,
20:05
issue custom categories and types,
20:07
and can be used when creating a new project.
20:10
During the project creation, it will ask you
20:12
if you want to use a template project to pull
20:14
all this information from.
20:15
So let's look at setting one of these up.
20:17
In Autodesk Docs, on the Templates tab,
20:20
all of the templates that you have created will be listed.
20:22
To create a new one, you simply click Create Project Template.
20:25
Now, you can either create a blank template
20:27
or you can create a template from an existing project.
20:30
So if you set up a project and you have things set up
20:32
kind of the way you want and you want to start there
20:34
with a template, you can copy those settings
20:36
from an existing project.
20:37
Once it's created, project templates
20:39
appear similar to regular projects.
20:41
So if we switch Autodesk Docs dropdown, where our account is,
20:45
to select projects.
20:46
We can also see templates.
20:48
If we select the template, you'll
20:49
notice we have something similar to what
20:51
we see within a project.
20:52
We have the Files tab and the Issues tab on files.
20:55
We can add those folders, use the ellipses
20:57
to set permissions, set up the issues, the custom properties
21:01
and the issues like we want, and add default roll permissions
21:04
that we want in this project.
21:05
That way when it comes time to create a new project,
21:07
we have a base to start from.
21:09
And we don't have to create everything
21:10
from scratch every time.
21:12
Let's jump into the demo on creating project templates.
21:15
We've now gone through and looked
21:16
at adding folders, adding permissions, adding users.
21:20
This is all set up that we can create a template from and use
21:24
in the future when we create other projects to make
21:26
another project much, much easier to set up.
21:28
Project templates can be created by account admins.
21:31
So you need to be more than a project admin,
21:33
you need to be an account admin on your Autodesk Construction
21:35
Cloud account.
21:36
I'm logged in here as the account admin.
21:38
I'm on the Templates tab.
21:39
Here we can create project templates.
21:42
So we'll just click this Create Project Template.
21:45
And it's going to ask us do we to create a blank template
21:47
or do we want to create a template from an existing
21:49
project?
21:50
Since we've set an existing project up
21:52
and we have some things that we want to template out of,
21:54
we're going to go ahead and say create
21:55
from an existing project.
21:57
Let's go ahead and give it a name.
21:60
We'll just give this a generic name, a typical project setup.
22:02
And now we need to select the project
22:04
that we're going to copy the settings from.
22:06
So we'll pick the one that we've been working in
22:08
and we'll click Create Template.
22:09
And it will go to work creating this template for us.
22:13
Once it's created, it'll take you here
22:14
to the template window.
22:16
On the configuration here--
22:17
this permissions is permissions for people who
22:20
have access to this template.
22:23
So I've got access as a project admin to this template.
22:29
If I want to add other people, the ability
22:31
to edit-- so only an account admin
22:33
can create the project template, but I can also
22:37
give other people access to edit the template once it's created.
22:40
So I could add that access here.
22:42
On the Details tab, I can change the name or I can archive it
22:45
so that this template cannot be used.
22:47
The layout of this template is going
22:49
to look very similar to a regular project.
22:51
So you'll notice here if I click this dropdown,
22:54
I'm on the project admin section.
22:56
There's also Docs in some of the other sections as well.
22:59
If I go to the Members tab here, I can now add members.
23:05
Any member that I add here will be automatically added
23:09
to every project created from this template.
23:11
So if I have maybe an internal team
23:13
or I've got some consultants that I typically always use,
23:16
I could add those members here so
23:17
that when I create a project from this template,
23:19
they're automatically added to the project.
23:23
I went ahead and added some people here.
23:25
So, in this case, maybe I've got a Structural Company, an MEP
23:29
Company that I typically work with
23:31
and I'm setting up a template that includes those users
23:35
and companies already in it.
23:36
I can do that right here.
23:37
So I just add people.
23:38
And it's just like I can figure them on a regular project.
23:41
I select the company, the role, the access level right here.
23:45
Now, any project I create from this,
23:47
these will be automatically added to it.
23:49
So I can also switch over to the Docs section here.
23:54
You'll notice I have a very similar layout.
23:57
I've got that permissions window here as well as the details.
23:60
I can come down here to the Files section
24:03
and here are those folders.
24:05
So these are the folders that existed on the project
24:07
that I selected when I created this template.
24:10
I can then modify this folder structure any way I want.
24:13
I can remove folders, subfolders,
24:15
rename them, add them, whatever I want to do.
24:18
I can also go to Permissions here and set some default
24:21
permissions.
24:22
Now, one thing to note with default permissions
24:24
on these project templates is you can only set up
24:27
roles as default permissions.
24:28
You can't set up users or companies
24:31
as defaults, permission levels, simply roles.
24:34
So this is something I don't use a ton because I like
24:36
to do my permissioning based off companies,
24:39
but you could add some role permissions here as well.
24:41
We jump over to the Issues tab, there
24:44
is also some templating work that we can do with the issue
24:48
category and type.
24:49
We can set those up for templates.
24:51
We can set our own custom issue categories and types
24:55
for issues that are then included in the template
24:57
so that we create a project from that template, that's
24:60
already created on the Issues tab for the project as well.
25:04
So once we have finished setting this template up,
25:08
we don't need to do anything further than that.
25:10
It can now be used.
25:11
That template can also be edited at any time.
25:14
So if, down the road, you decide that you
25:15
need to change out the folder structure
25:17
or do something different with it,
25:18
you can always come back into that template
25:21
and modify the settings, that any projects
25:23
you create from it from there forward we'll
25:26
will those new settings.
25:27
So this can save you a ton of time when it
25:29
comes to setting a project up.
25:31
If you template some of this stuff out beforehand,
25:33
it'll give you a leg up on getting your project created.
25:35
You'll already have folders in place,
25:37
you could have people added to it,
25:39
really gets you a step forward when it
25:41
comes to setting projects up.
25:42
And with that, thank you for joining Autodesk Accelerator,
25:45
there's some additional resources available to you.
25:47
On the Customer Success Hub-- customersuccess.autodesk.com--
25:51
there's more courses, learning paths,
25:53
recorded coaching sessions, some more live coaching topics.
25:56
They're similar topics to this as well as
25:58
topics across the entire Autodesk platform.
26:01
That's all available to you on the Customer Success Hub,
26:03
so go check it out.
26:04
And with that, thanks for joining this session
26:06
and have a fantastic day.
Video transcript
00:00
[MUSIC PLAYING]
00:11
BRYSON ANDERSON: Autodesk Accelerators
00:12
are designed to help your team stay ahead
00:14
of the curve with the latest workflows.
00:16
These include on-demand courses, prerecorded coaching,
00:19
as well as live coaching.
00:20
To see the full list of topics, visit the Customer Success Hub.
00:25
Take a moment to read over the safe harbor statement.
00:28
This is a reminder that we may make statements
00:29
about future developments, these are not
00:31
intended to be a guarantee but reflect
00:33
our current expectations and assumptions.
00:38
Before we get started, let me introduce myself.
00:40
My name is Bryson Anderson.
00:41
I'm based out of Utah, been in the IT industry
00:44
for about 14 years now, the last 10 years
00:46
in the AEC Marketplace working with firms
00:49
in all aspects of their IT, including
00:51
data management and collaboration
00:52
for Autodesk workflows.
00:55
Welcome to the Autodesk Accelerator,
00:57
set folder structures and permissions in Autodesk Docs.
00:60
The learning objectives for the session
01:02
is to understand how to create an organized folder structure,
01:04
understand how to assign permission
01:06
and access to folders, learn how to accept invitations
01:09
to Autodesk Docs.
01:11
The workflow we're going to follow
01:12
is accept project admin invite from the account admin,
01:15
create an organized folder structure,
01:17
invite and assign users access to directories,
01:20
assign permission levels, accept user invite from the project
01:23
admin, and subscribe to folders for email notifications.
01:28
So let's start with our first step,
01:30
creating an organized folder structure.
01:32
This is going to be the first step in our workflow.
01:35
When setting up a project, one of the first things
01:37
we need to do is create a folder structure.
01:39
You probably already have a project folder structure
01:41
and that's a really good place to start from.
01:43
A couple of things you want to keep in mind as you're
01:44
setting up a BIM 360 project.
01:46
You want to lay out folders to support your workflow
01:48
for collaborating with other companies,
01:50
so whether that means creating folders for companies
01:52
or folders for disciplines.
01:55
And keep permissions in mind.
01:56
Your folder structure should allow
01:57
you to set access permissions to meet your project requirements.
01:60
So, for example, if you've got subconsultants
02:02
that should only have read to some folders
02:04
and write to others.
02:06
You'll want to subfolder those correctly
02:07
so that you can set those permissions.
02:09
There are a couple of ways to create folder structures.
02:11
The first way is to manually create the folder
02:13
structure in Autodesk Docs.
02:15
On the Files tab, you'll have two default locations
02:18
for the field and project files.
02:20
To create a subfolder underneath either of those--
02:22
if you hover over them, you'll see these three dots here,
02:25
this ellipsis.
02:25
When you hover over that and click,
02:27
you'll have some options.
02:29
One of those is to add a subfolder.
02:31
When you click Add Subfolder, a subfolder is created.
02:34
You can then change the name and hit the checkbox
02:36
to finish and then keep going down through,
02:38
adding subfolders and additional folders as needed.
02:41
All of the options for adding folders, renaming them,
02:44
deleting them can all be found by hovering over the folder,
02:47
clicking on the ellipsis, and then picking,
02:49
rename, add subfolder, whatever is that you want to do.
02:52
Now, if you have a large folder structure
02:54
or you have a folder structure that already exists,
02:56
maybe you've got it on your local server
02:57
already, another way that you can
02:59
add these is by actually uploading
03:01
the folders through the Autodesk Desktop Connector.
03:03
The Desktop Connector is an application
03:05
that you install on your computer
03:06
and it connects the Autodesk Docs to your Windows File
03:09
Explorer so that you can easily copy things
03:12
from one location to the other.
03:13
If you've already created an existing folder structure,
03:15
all you've got to do is just drag and drop it
03:17
from your local location over to the project files location.
03:20
As you're doing this, you'll want
03:21
to either drag and drop or do a Control-C, Control-V shortcut
03:25
for copy and paste.
03:26
Because when you right click in the Desktop Connector folder,
03:29
you don't get the same menu that you get inside of Windows.
03:31
There's not a paste.
03:33
So when you copy it out of File Explorer,
03:36
in order to paste it into the Desktop Connector,
03:39
either drag and drop it or use Control-V, the keyboard
03:42
shortcut, for pasting.
03:43
Once you've got that folder structure moved over
03:45
to the Desktop Connector location,
03:47
you can add more folders through here
03:49
or through the web browser.
03:51
You can do it either way.
03:52
Now that we have a folder structure,
03:54
we can move on to the next step--
03:55
to set intuitive organized permissions.
03:59
This is going to be our second step in the workflow.
04:01
A couple of things to consider when
04:02
you're looking at permissioning out your folders.
04:04
Project admins have full access to every file in every folder.
04:08
As a project admin they're unrestricted,
04:09
you cannot restrict them.
04:11
So keep your project admins more to a minimum,
04:13
realizing that they have full access to everything.
04:16
Permissions are also set by folder and subfolder.
04:19
They're not set by the individual file.
04:21
When you set permissions on a folder,
04:23
all of the folders underneath it will inherit the permissions
04:26
that you set on that parent folder.
04:27
You can then drill down and change subfolder permissions
04:30
as you need.
04:31
Permissions can be set by either individual users, companies,
04:35
or roles.
04:36
You can use one or a mix of all the types.
04:38
But when you get into using lots of companies, and users,
04:41
and roles, it can get a little bit confusing about where
04:44
permissions are coming from.
04:45
If you've got a person added by a company, and by a role,
04:48
and by the individual user, it can get a little bit messy
04:50
when you're trying to figure out why someone does or does not
04:52
have permissions.
04:53
I try to keep my permissions as simple as possible,
04:55
using things like company and roles
04:58
as groups to add permissions and only adding users individually
05:01
when I really need to.
05:02
You'll also want to think about software-specific workflows
05:05
and permissions required.
05:06
So, for example, Revit Cloud Worksharing in BIM Collaborate
05:09
Pro.
05:09
Users are going to need view and download to link a Revit model.
05:12
So you'll want to kind of think all these things through
05:14
as you're getting your folder structure set up and getting
05:16
things permissioned out.
05:17
Permissions are set in Autodesk Docs
05:19
on the Files tab, same place where we created subfolders.
05:23
If you click those ellipsis, one of the options is permissions.
05:26
If you click on Permissions, it will pop out
05:28
the permissions window and you can start
05:30
setting those permissions.
05:31
You can use the companies and roles,
05:33
like we talked about earlier, to create groups to make things
05:35
easier and more scalable so that down the road, if you
05:38
add a company with permissions to a folder
05:40
and then you invite someone else from that company,
05:42
you don't have to come in and remember to add them
05:44
individually to permissions.
05:45
They'll inherit permissions based on that company or role
05:47
that they're assigned to.
05:49
One thing to keep in mind is that the highest access
05:51
granted wins.
05:52
So, for example, if you had company settings at view
05:55
but you invited the individual user
05:56
and gave them higher permissions,
05:58
they would have those higher permissions.
06:00
There are four categories of permissions-- view,
06:02
create, edit, and manage.
06:05
And there's different levels within those categories.
06:07
If you have no permission set at all,
06:09
then the user can't see the folder.
06:11
To add someone, click the Add button and type
06:14
in the either username, the company, or the role.
06:17
And then you'll use this dropdown
06:19
to select what permission level you want to give them.
06:21
So, for example, under view we have view only,
06:23
and view+download.
06:24
And similarly, in create, one level
06:27
does not have permissions to upload while the other does.
06:29
So select the permission level that you want
06:31
and then continue on adding permissions.
06:34
Let's jump into the demo video on setting up
06:36
folders and permissions.
06:38
Creating an organized folder structure
06:39
is key to project setup.
06:41
You'll want to lay out your folders
06:42
to support your workflows, including collaborating
06:44
with other companies.
06:46
Your current project folder structure
06:47
is probably a really great place to start from.
06:49
You likely already have a folder structure
06:51
that you use on projects.
06:53
Starting with that gives you a really good base
06:56
and you can build on it from there.
06:58
As you begin setting up your project folder structure,
07:00
one key thing to consider is who's
07:02
going to be involved in this project.
07:04
Is it just an internal project or they'll
07:06
be outside consultants involved?
07:08
That will help dictate what kind of folder structure you set up.
07:11
To do this, we're going to use the Autodesk Desktop Connector.
07:14
The Desktop Connector is a utility
07:15
that connects the Autodesk Docs folders with your Windows File
07:20
Explorer.
07:20
So we're looking at that here.
07:22
On the right hand side, I'm browsed into my Desktop
07:25
Connector location.
07:26
On the left hand side, I have a local folder template.
07:29
These are just empty folders that I can copy and paste
07:33
from my local directory over into Desktop Connector, which
07:37
will then upload them into Autodesk Docs.
07:40
Now one thing to note as you're doing
07:41
this is when you right click in Windows File Explorer,
07:44
you get all kinds of options, including copy and paste.
07:47
When you right click in Desktop Connector
07:49
you have the option to create a new folder,
07:50
but your right click context menu is different.
07:53
So to copy and paste over, you need to either highlight, drag
07:56
and drop, or use your shortcut keys Control-A
08:00
to select all, Control-C to copy, Control-V to paste.
08:04
I like to just select and drag and drop.
08:07
And you'll notice down here the Desktop Connector is
08:10
going to tell us that it's transferring
08:12
those folders over.
08:13
It's creating that folder structure on the cloud,
08:15
much easier than creating them manually one by one.
08:18
We can use what we already have in Windows Explorer
08:20
or just create in Windows File Explorer
08:23
a directory and then copy and paste it over.
08:26
Jumping back over to Autodesk Docs,
08:28
I copy those into a folder called Files.
08:31
And you'll see that folder structure created here.
08:34
I can then modify that here in Autodesk Docs or I
08:37
can go back to my Desktop Connector location
08:39
here and modify file names or folder names by doing a rename,
08:44
add new folders, copy and paste other folders over,
08:48
however I want to do that.
08:49
Once I've got my folder structure created,
08:51
I need to think about permissions.
08:53
So if I hover over any of these folders
08:55
and click these three dots, I can then go to Permissions.
08:60
So items are permissioned by folder
09:03
and not by file in Autodesk Docs.
09:05
So I'm going to actually set folder permissions
09:07
that wherever files exist within that folder
09:09
are dictated by the folder permissions.
09:11
I can assign out permissions by either individual users,
09:14
by companies, or by roles.
09:16
I also have four different categories
09:19
of permission types--
09:20
view permissions, create permissions, edit permissions,
09:24
and manage permissions.
09:26
Under view and create, you'll notice I
09:27
have a couple different types--
09:29
view only or view and download.
09:30
And then on the create type whether or not I
09:32
want people to be able to upload or not.
09:34
So I've got all kinds of permission settings that I
09:36
can permission based on these users or group types,
09:39
if you will, companies, and roles.
09:41
Typically, I like to permission things
09:42
out as much as I can using companies, roles
09:45
as kind of secondary grouping, and then
09:48
adding users one by one if I really need to.
09:50
But adding by companies makes my permissions really modular.
09:53
So, in the future, if I have, say,
09:56
MEP Company added here a few permissions
09:58
and I add somebody to the MEP Company,
10:01
I don't have to remember to go give them folder permissions.
10:03
They're going to have folder permissions already set
10:05
by their company.
10:07
This really helps with scalability
10:08
so that as you add and remove people from projects,
10:11
add and move them from companies or roles,
10:13
permissions to folders are automatically handled.
10:15
Now, you'll notice a couple of things in here.
10:17
First of all, on this user, it tells me it's a project admin
10:21
and they remove button is not there.
10:23
So any project administrator will have full access
10:26
to all folders within the project
10:29
that they are a project admin for.
10:31
It's not something that you can configure or lessen
10:33
their permissions.
10:34
That's just how this works.
10:36
Built into the system is all project
10:38
administrators have default access to everything.
10:41
So you'll want to make sure that you keep your project
10:43
administrators to a minimum so you're not
10:45
leaving every folder wide open to everybody.
10:47
In this scenario, this is the architectural folder.
10:50
So I gave the architectural company edit permissions.
10:52
I gave the Structural and MEP company view permissions.
10:56
I've got full permissions because I'm
10:58
a project administrator.
10:59
And then I gave Shawn manage.
11:01
So the manage permission level gives them
11:04
the ability that can change folder permissions
11:06
on their folder.
11:07
So if they're not an administrator,
11:09
but I want them to be able to manage
11:10
who has access to their folder and change that,
11:13
I can give them manage permissions.
11:14
They then have full edit permissions as well as
11:17
the ability to manage who has access to the folder.
11:21
Adding additional permissions is easy.
11:23
You click the Add button, put in the name--
11:25
either by their name or by their email
11:27
address-- the role, or the company.
11:29
So I could select the role of project engineer
11:33
and give that a permission level.
11:35
We'll say we want project engineers
11:37
to have view and download.
11:41
Click Add and we'll add them here to the list.
11:43
If I need to remove permissions, I can simply just click Remove.
11:47
As I add permissions to folders, you'll
11:50
notice subfolders underneath are going
11:52
to inherit those permissions.
11:53
So if I click on this Consumed folder, or the Dynamo,
11:56
or FormIt folders underneath architecture.
11:59
You'll notice that it's saying inherited.
12:02
It's not given the ability to remove that permission level.
12:07
I can, however, give them more permissions on a subfolder.
12:11
So, for example, under MEP Company, who has view,
12:14
I could give them create, edit, or manage on this folder.
12:17
I cannot go backwards.
12:18
Notice view only as grayed out.
12:20
If I go to Shawn here, who has manage,
12:23
you'll notice I can't change anything.
12:25
So I can add additional permissions to subfolders,
12:28
but I can't restrict to a lower permission level on subfolders.
12:32
So keep that in mind as you lay out folders,
12:35
understanding that subfolders of that folder--
12:38
you can add additional permissions to the subfolders,
12:41
but you can't restrict to a lower permission level.
12:45
Let's also talk about permission levels
12:46
in the For the Field folder.
12:49
So For the Field folder is a specialized folder that
12:52
has a specialized workflow.
12:53
Anything put in For the Field is synced to mobile devices.
12:57
Some of the other Autodesk Construction Cloud applications
12:59
like plan grid and build have specialized workflows
13:02
for this folder.
13:03
Keep in mind also that BIM Collaborate Pro
13:05
tools, like Revit Cloud Worksharing
13:07
and the collaboration for Civil 3D and Plant 3D,
13:10
requires that files be in project files.
13:12
If you put them in For the Field,
13:14
they're not accessible through those applications.
13:16
So when you add things to For the Field,
13:17
just be sure you know what the use case is
13:20
for it being in For the Field.
13:22
It's basically a place for a virtualized document plan set
13:25
to have in the field is stored.
13:27
But permissions are a little bit different For the Field area.
13:30
So let's go ahead and click on For the Field.
13:32
We've got one PDF file in here.
13:35
So let's click on the permissions.
13:39
You'll notice we have an everyone in here
13:42
and it's not removable.
13:44
And if we go to the permissions, we
13:46
can't give it anything higher than view or view and download.
13:49
Those are our two options.
13:51
Does everyone have view only or view and download?
13:53
We can't change anything else on the everyone category here.
13:57
That is by design from For the Field.
13:59
It even gives you the little message
14:01
here across the top that files in this folder
14:03
are available to all project members and their synced
14:05
to mobile devices.
14:06
So keep in mind--
14:08
anything you put in For the Field everybody
14:10
has view access to.
14:12
Now, you can give others higher access than that.
14:15
So we could come in here and we could say let's give Shawn
14:20
some higher permissions.
14:21
We'll give him edit permissions.
14:25
And now Shawn has edit permissions on this folder.
14:28
So one thing to note with adding people
14:31
by group and by individual name here--
14:33
so both Shawn and I are going to be part of the everyone group,
14:36
but we're also added individually here as users.
14:39
So whatever the highest permission
14:40
level given to the user is is what will win.
14:43
So, in this case, the group permission is giving it view.
14:47
But Shawn's got edit permissions through user base
14:49
permissioning, so he'll have edit on this folder.
14:52
You'll want to go through, set up your permissions
14:54
in For the Field, set them up in project files,
14:56
get that structure just the way you want it for your project,
14:59
and then it's time to go start adding members.
15:02
Next, we're going to look at inviting users
15:04
to Autodesk Docs.
15:07
This is going to be the third step in our workflow.
15:10
Any user that needs access to Autodesk Docs
15:12
needs to be invited to the project by a project admin.
15:14
Admins can invite members from the Members tab in Docs
15:17
or from the project admin console.
15:19
When adding members, you can add them one by one
15:21
or you can upload them through a list.
15:25
So if you have an existing list of members
15:26
that need to be added, instead of typing them one by one,
15:29
you can upload that list and add them.
15:30
When you add members, you need to specify
15:32
the company, the role, and whether or not
15:34
they're going to have admin rights,
15:36
as well as give them product access required
15:38
for their access needs to Autodesk Docs.
15:40
Once you have that configured, you can click Add
15:43
and it will send them a welcome email.
15:47
You can view your existing users on the Members tab in project
15:50
admin or in Autodesk Docs.
15:51
And you can change any of the settings
15:53
that you want-- the company, the role, their access
15:55
level, their assigned products.
15:57
Those can be edited by a project admin any time.
16:01
As I mentioned earlier, all members
16:03
are going to get a welcome email.
16:04
Each invited user will receive a welcome email like you see here
16:07
on the right hand side.
16:08
Depending on if the user has been
16:10
added to a project on your account before or not,
16:12
this little blue button down here at the bottom
16:14
may read differently.
16:15
On this one, this user invited had not been added to a project
16:18
before and so they need to click Activate Membership to finish
16:21
joining that project.
16:23
Otherwise, it would say join the project or something similar.
16:27
Let's jump into the demonstration
16:28
on adding members.
16:30
Now that we've got a folder structure and permissions
16:32
in place, let's start adding some members.
16:34
Adding someone is very simple.
16:36
We just click the Add Members button here
16:38
on the Members tab of Docs.
16:40
We could also go to the project admin
16:43
and go to the Members tab of project admin.
16:46
It's going to give us the same thing in either place.
16:48
In order to add members to a project,
16:50
you do need to be a project admin.
16:52
So if you are in the Docs here and you go to members
16:57
and you are not in admin, you'll won't have an Add Members
16:60
button here.
17:00
You will see the list of members on the project,
17:03
but you will not be able to add members to the project.
17:06
I am a project admin, so I do see the Add Members.
17:09
I'll go ahead and click that.
17:11
So to add somebody, we just need to enter their email address.
17:14
If the person we're adding is already
17:16
a member of our account, so they've
17:18
been added to another project, the account actually
17:21
creates a directory of people that
17:23
have been involved in projects on that directory before.
17:27
So when we go to start typing, for example, you'll notice here
17:30
is me, I'm already in the project.
17:33
Here's somebody else, who's been added to another project,
17:36
so they're already in our project directory,
17:38
so we could just select them.
17:40
If we haven't added them to any project on our account
17:43
in the past, we'll just type in their email address, hit Enter,
17:47
and we'll get to the same thing here.
17:49
So we will add this user.
17:51
The next thing to do is assign them to a company.
17:53
So if you remember, as we are setting up our permissions,
17:56
we set up a lot of permissions based on company.
17:58
So adding someone to a company here is going to do two things.
18:01
One, organize them into that company
18:03
but also give them folder permissions based
18:06
on that company we set.
18:07
So let's go ahead and add him to the Structural Company.
18:11
Now, the same thing goes for roles.
18:12
We've got a whole bunch of roles here.
18:14
These are all the default roles.
18:15
You can-- project administrators can configure their own roles.
18:19
So if you want to set a custom set of roles, you can do that.
18:21
We'll select something here.
18:24
How about we say he is an engineer.
18:25
If we have folder permissions based on roles,
18:28
that will also give him permissions based on that.
18:31
Then we need to select whether they are a project member
18:33
or a project administrator.
18:35
Keep in mind that administrator has full access to everything,
18:38
so keep those to a minimum.
18:40
We'll set this one as a project member.
18:42
The last thing that we need to do here
18:44
is assign them to products.
18:46
So we need to give them at least Docs.
18:49
Docs is that base location where everything is stored.
18:52
So to do anything, they need to have that Docs platform.
18:56
We also can assign any other modules, so
18:58
the Design Collaboration module, Model Coordination.
19:01
We'll leave this one at just Docs.
19:03
And we click Add.
19:05
This message will tell us that it's adding members
19:07
and then it might take just a moment to do that.
19:09
After a couple of seconds, we'll see that user here in the list,
19:12
that they were added moments ago.
19:13
That user is also going to get a welcome email
19:16
like this, says welcome to the project with a link
19:19
to the project.
19:20
This message is a little bit different for this user
19:22
because this user was already added to the account.
19:24
If they were not added to our account,
19:26
this button would look a little bit different.
19:27
It would have had an activate your membership
19:29
or other message here telling them
19:31
they need to join the project.
19:32
They click that link to join the project,
19:35
they're now added to the account and have
19:36
access to that project.
19:39
Once they log into Docs and go to the Files section,
19:43
they'll be able to see any folders
19:45
and files in those folders that they've been given access to.
19:50
Jumping into our final topic, create project templates.
19:53
Again, this is going to be the final step in our workflow.
19:57
One of the things we can do to simplify and speed up
19:59
our project creation in the future is to create templates.
20:02
Templates can contain folders and permissions, members,
20:05
issue custom categories and types,
20:07
and can be used when creating a new project.
20:10
During the project creation, it will ask you
20:12
if you want to use a template project to pull
20:14
all this information from.
20:15
So let's look at setting one of these up.
20:17
In Autodesk Docs, on the Templates tab,
20:20
all of the templates that you have created will be listed.
20:22
To create a new one, you simply click Create Project Template.
20:25
Now, you can either create a blank template
20:27
or you can create a template from an existing project.
20:30
So if you set up a project and you have things set up
20:32
kind of the way you want and you want to start there
20:34
with a template, you can copy those settings
20:36
from an existing project.
20:37
Once it's created, project templates
20:39
appear similar to regular projects.
20:41
So if we switch Autodesk Docs dropdown, where our account is,
20:45
to select projects.
20:46
We can also see templates.
20:48
If we select the template, you'll
20:49
notice we have something similar to what
20:51
we see within a project.
20:52
We have the Files tab and the Issues tab on files.
20:55
We can add those folders, use the ellipses
20:57
to set permissions, set up the issues, the custom properties
21:01
and the issues like we want, and add default roll permissions
21:04
that we want in this project.
21:05
That way when it comes time to create a new project,
21:07
we have a base to start from.
21:09
And we don't have to create everything
21:10
from scratch every time.
21:12
Let's jump into the demo on creating project templates.
21:15
We've now gone through and looked
21:16
at adding folders, adding permissions, adding users.
21:20
This is all set up that we can create a template from and use
21:24
in the future when we create other projects to make
21:26
another project much, much easier to set up.
21:28
Project templates can be created by account admins.
21:31
So you need to be more than a project admin,
21:33
you need to be an account admin on your Autodesk Construction
21:35
Cloud account.
21:36
I'm logged in here as the account admin.
21:38
I'm on the Templates tab.
21:39
Here we can create project templates.
21:42
So we'll just click this Create Project Template.
21:45
And it's going to ask us do we to create a blank template
21:47
or do we want to create a template from an existing
21:49
project?
21:50
Since we've set an existing project up
21:52
and we have some things that we want to template out of,
21:54
we're going to go ahead and say create
21:55
from an existing project.
21:57
Let's go ahead and give it a name.
21:60
We'll just give this a generic name, a typical project setup.
22:02
And now we need to select the project
22:04
that we're going to copy the settings from.
22:06
So we'll pick the one that we've been working in
22:08
and we'll click Create Template.
22:09
And it will go to work creating this template for us.
22:13
Once it's created, it'll take you here
22:14
to the template window.
22:16
On the configuration here--
22:17
this permissions is permissions for people who
22:20
have access to this template.
22:23
So I've got access as a project admin to this template.
22:29
If I want to add other people, the ability
22:31
to edit-- so only an account admin
22:33
can create the project template, but I can also
22:37
give other people access to edit the template once it's created.
22:40
So I could add that access here.
22:42
On the Details tab, I can change the name or I can archive it
22:45
so that this template cannot be used.
22:47
The layout of this template is going
22:49
to look very similar to a regular project.
22:51
So you'll notice here if I click this dropdown,
22:54
I'm on the project admin section.
22:56
There's also Docs in some of the other sections as well.
22:59
If I go to the Members tab here, I can now add members.
23:05
Any member that I add here will be automatically added
23:09
to every project created from this template.
23:11
So if I have maybe an internal team
23:13
or I've got some consultants that I typically always use,
23:16
I could add those members here so
23:17
that when I create a project from this template,
23:19
they're automatically added to the project.
23:23
I went ahead and added some people here.
23:25
So, in this case, maybe I've got a Structural Company, an MEP
23:29
Company that I typically work with
23:31
and I'm setting up a template that includes those users
23:35
and companies already in it.
23:36
I can do that right here.
23:37
So I just add people.
23:38
And it's just like I can figure them on a regular project.
23:41
I select the company, the role, the access level right here.
23:45
Now, any project I create from this,
23:47
these will be automatically added to it.
23:49
So I can also switch over to the Docs section here.
23:54
You'll notice I have a very similar layout.
23:57
I've got that permissions window here as well as the details.
23:60
I can come down here to the Files section
24:03
and here are those folders.
24:05
So these are the folders that existed on the project
24:07
that I selected when I created this template.
24:10
I can then modify this folder structure any way I want.
24:13
I can remove folders, subfolders,
24:15
rename them, add them, whatever I want to do.
24:18
I can also go to Permissions here and set some default
24:21
permissions.
24:22
Now, one thing to note with default permissions
24:24
on these project templates is you can only set up
24:27
roles as default permissions.
24:28
You can't set up users or companies
24:31
as defaults, permission levels, simply roles.
24:34
So this is something I don't use a ton because I like
24:36
to do my permissioning based off companies,
24:39
but you could add some role permissions here as well.
24:41
We jump over to the Issues tab, there
24:44
is also some templating work that we can do with the issue
24:48
category and type.
24:49
We can set those up for templates.
24:51
We can set our own custom issue categories and types
24:55
for issues that are then included in the template
24:57
so that we create a project from that template, that's
24:60
already created on the Issues tab for the project as well.
25:04
So once we have finished setting this template up,
25:08
we don't need to do anything further than that.
25:10
It can now be used.
25:11
That template can also be edited at any time.
25:14
So if, down the road, you decide that you
25:15
need to change out the folder structure
25:17
or do something different with it,
25:18
you can always come back into that template
25:21
and modify the settings, that any projects
25:23
you create from it from there forward we'll
25:26
will those new settings.
25:27
So this can save you a ton of time when it
25:29
comes to setting a project up.
25:31
If you template some of this stuff out beforehand,
25:33
it'll give you a leg up on getting your project created.
25:35
You'll already have folders in place,
25:37
you could have people added to it,
25:39
really gets you a step forward when it
25:41
comes to setting projects up.
25:42
And with that, thank you for joining Autodesk Accelerator,
25:45
there's some additional resources available to you.
25:47
On the Customer Success Hub-- customersuccess.autodesk.com--
25:51
there's more courses, learning paths,
25:53
recorded coaching sessions, some more live coaching topics.
25:56
They're similar topics to this as well as
25:58
topics across the entire Autodesk platform.
26:01
That's all available to you on the Customer Success Hub,
26:03
so go check it out.
26:04
And with that, thanks for joining this session
26:06
and have a fantastic day.
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.