Transcript
00:10
Within each permission rule,
00:11
permissions are broken down into entity, field, app, and advanced permissions.
00:17
Entity permissions control
00:19
if users can see entities, create entities, delete entities, and edit entities.
00:26
For example,
00:27
perhaps an artist will be able to see assets but
00:30
only managers will be able to create or delete them.
00:34
Field permissions control if users can see fields and edit fields.
00:39
Each entity has its own set of fields.
00:42
An example of a field control would be a budget field on a task.
00:46
Artists can be restricted from seeing the field altogether.
00:49
Managers can be allowed to see but not edit the field.
00:53
Admins can see and edit the field.
00:56
This way cost information is only shared on a need to
00:59
know basis but can still be stored in Flow Production Tracking.
01:04
App permissions control if users can access an app or not.
01:10
Advanced permissions control
01:12
if users have access to specific functionality across Flow Production Tracking,
01:16
such as seeing all projects,
01:18
editing the project navigation menu, and creating and saving project pages.
01:23
Permission roles are designed to be optimized for user type. People with
01:27
similar roles will ideally be a part of the same permission roles.
01:31
Maintaining permission roles can be complicated,
01:33
so it is generally advised not to have too many roles on
01:37
a site and to avoid creating per project or per department roles.
01:41
The default roles also come with some
01:43
conditional rules to further restrict access.
01:46
An example of a conditional rule is that the vendor permission role
01:49
can only see a task if they are assigned to it.
01:53
The control over entity, field, app, and advanced permissions is
01:58
what makes each permission role different from one another.
00:10
Within each permission rule,
00:11
permissions are broken down into entity, field, app, and advanced permissions.
00:17
Entity permissions control
00:19
if users can see entities, create entities, delete entities, and edit entities.
00:26
For example,
00:27
perhaps an artist will be able to see assets but
00:30
only managers will be able to create or delete them.
00:34
Field permissions control if users can see fields and edit fields.
00:39
Each entity has its own set of fields.
00:42
An example of a field control would be a budget field on a task.
00:46
Artists can be restricted from seeing the field altogether.
00:49
Managers can be allowed to see but not edit the field.
00:53
Admins can see and edit the field.
00:56
This way cost information is only shared on a need to
00:59
know basis but can still be stored in Flow Production Tracking.
01:04
App permissions control if users can access an app or not.
01:10
Advanced permissions control
01:12
if users have access to specific functionality across Flow Production Tracking,
01:16
such as seeing all projects,
01:18
editing the project navigation menu, and creating and saving project pages.
01:23
Permission roles are designed to be optimized for user type. People with
01:27
similar roles will ideally be a part of the same permission roles.
01:31
Maintaining permission roles can be complicated,
01:33
so it is generally advised not to have too many roles on
01:37
a site and to avoid creating per project or per department roles.
01:41
The default roles also come with some
01:43
conditional rules to further restrict access.
01:46
An example of a conditional rule is that the vendor permission role
01:49
can only see a task if they are assigned to it.
01:53
The control over entity, field, app, and advanced permissions is
01:58
what makes each permission role different from one another.
Within each role, permissions are broken down into Entity, Field, App, and Advanced permissions.
Entity permissions control if users can:
For example, perhaps an Artist will be able to see Assets, but only Managers will be able to create or delete them.
Field permissions control if users can:
Each entity has its own set of fields. An example of a field control would be a budget field on a task. Artists can be restricted from seeing the field altogether. Managers can be allowed to see but not Edit the field. Admins can see and edit the field. This way cost information is only shared on a need-to-know basis but can still be stored in Flow Production Tracking.
App permissions control if users can:
Advanced permissions control if users have access to specific functionality across Flow Production Tracking, such as:
Permission roles are designed to be optimized for user-type. People with similar roles will ideally be a part of the same permission roles. Maintaining permission roles can be complicated, so it is generally advised not to have too many roles on a site, and to avoid creating per project or per department roles.
The default roles also come with some conditional rules to further restrict access. An example of a conditional rule is that the Vendor permission role can only see a task if they are assigned to it.
