& Construction

Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
& Manufacturing

Professional CAD/CAM tools built on Inventor and AutoCAD
Transcript
00:08
Permissions define what users can see and the
00:11
actions that users can perform in
00:14
Flow Production Tracking.
00:15
Your permission role will define what fields, entities, and apps
00:19
you can see and which actions you can perform.
00:22
When you're assigned a permission role, admins can see
00:24
the tasks you might be asked to complete
00:27
or the information you may need to access to define which role you're best
00:30
suited for. Flow production tracking ships with
00:33
a handful of built in permission roles.
00:35
Admins have the highest level of access and control over Flow Production Tracking.
00:41
Admins are followed by managers and then by artists,
00:45
while vendors have the lowest level of access.
00:48
Admins have complete control over all operations and flow production tracking.
00:53
With the only exceptions being modifying things that are
00:56
required by the system such as deleting a template
00:58
project.
00:60
Managers share most functionality with admins but
01:03
have certain entities restricted by default.
01:05
For example, managers cannot create new fields, whereas admins can.
01:11
Artists can only see projects that they are specifically assigned to.
01:15
Artists can update or edit notes if they are the author of that note,
01:19
status fields on tasks
01:21
they are assigned to,
01:22
and versions, time logs, and tickets, if they are the creator of those entities.
01:27
Vendors can only see projects that they are specifically assigned to.
01:31
Additionally, vendors can only see tasks that they or a group that they are in
01:36
are assigned to, shots and assets if they are assigned
01:39
to a task on that shot or asset, notes
01:42
if they are in the To or CC field,
01:44
or if they created the note, as well as versions that they create. Typical
01:49
personas for each role might include the
01:51
following: for the admin role site administrators,
01:54
pipeline TDs and IT members who need to
01:57
configure site settings for the manager, role, producers, supervisors,
02:02
managers,
02:02
coordinators, and leads who need access to create and
02:05
update pages and permission to update all project level information.
02:10
For the artist role,
02:11
artists or anyone who is assigned to tasks who will be
02:14
using Flow Production Tracking to track their daily workload and tasks,
02:18
read and write notes and submit work. For the vendor role, outsource teams and
02:23
vendors who we don't want to access any work that they aren't assigned to.
00:08
Permissions define what users can see and the
00:11
actions that users can perform in
00:14
Flow Production Tracking.
00:15
Your permission role will define what fields, entities, and apps
00:19
you can see and which actions you can perform.
00:22
When you're assigned a permission role, admins can see
00:24
the tasks you might be asked to complete
00:27
or the information you may need to access to define which role you're best
00:30
suited for. Flow production tracking ships with
00:33
a handful of built in permission roles.
00:35
Admins have the highest level of access and control over Flow Production Tracking.
00:41
Admins are followed by managers and then by artists,
00:45
while vendors have the lowest level of access.
00:48
Admins have complete control over all operations and flow production tracking.
00:53
With the only exceptions being modifying things that are
00:56
required by the system such as deleting a template
00:58
project.
00:60
Managers share most functionality with admins but
01:03
have certain entities restricted by default.
01:05
For example, managers cannot create new fields, whereas admins can.
01:11
Artists can only see projects that they are specifically assigned to.
01:15
Artists can update or edit notes if they are the author of that note,
01:19
status fields on tasks
01:21
they are assigned to,
01:22
and versions, time logs, and tickets, if they are the creator of those entities.
01:27
Vendors can only see projects that they are specifically assigned to.
01:31
Additionally, vendors can only see tasks that they or a group that they are in
01:36
are assigned to, shots and assets if they are assigned
01:39
to a task on that shot or asset, notes
01:42
if they are in the To or CC field,
01:44
or if they created the note, as well as versions that they create. Typical
01:49
personas for each role might include the
01:51
following: for the admin role site administrators,
01:54
pipeline TDs and IT members who need to
01:57
configure site settings for the manager, role, producers, supervisors,
02:02
managers,
02:02
coordinators, and leads who need access to create and
02:05
update pages and permission to update all project level information.
02:10
For the artist role,
02:11
artists or anyone who is assigned to tasks who will be
02:14
using Flow Production Tracking to track their daily workload and tasks,
02:18
read and write notes and submit work. For the vendor role, outsource teams and
02:23
vendors who we don't want to access any work that they aren't assigned to.
Permissions define what users can see and the actions that users can perform in Flow Production Tracking.
When a user is assigned a permission role, Admins consider the tasks they might be asked to complete, or the information they may need to access, to define which role they are best suited for.
Flow Production Tracking ships with a handful of built-in permission roles. Admins have the highest level of access and controls over Flow Production Tracking. Admins are followed by Managers, then by Artists. Vendors have the lowest level of access.