Grass Valley Aurora Edit LD v.6.5 Installation - Manual (Page 72)

58
Aurora Edit Installation Guide November 25, 2008
Chapter 1 Aurora Edit Security
Designing a security schema
In order to set up security in your SAN system you need create a schema for permissions.
The schema determines which groups you create, and which permissions you give each
group.
Thomson Grass Valley has created a typical schema for use in illustrating security
principles in this document. You may use this schema if it is appropriate for your
newsroom, or create your own. For the examples in this manual, we’ll assume that the
newsroom has five groups: Editors, Producers, Archivists, Ingestors, and Viewers.
The SAN security principles are agnostic to these groups, though the use of groups
greatly simplifies the establishment of the security schema. We picked these names as
exemplary; you do not need to use them in your operation. You can have as many or as
few groups as you like, named however you wish. If your domain has a tree hierarchy,
you may assign permissions to global groups as well.
Sample security schema
The following table lists the groups and permissions being used as an example in this
document:
News Group Bin Permissions
Domain Administrator All Full control
Editors Monday-Sunday Read/Write/Delete in top level bins, but cannot
delete material from newscast bins.
Feeds Read only
HFR Read/Write
Archive Read/Write
Producers Monday-Sunday Read/Write
Feeds Read only
HFR Full control
Archive Read/Write
Archivists Monday-Sunday Read only
Feeds Read/Write
HFR Read only
Archive Full control
Ingestors Monday-Sunday Read only
Feeds Full control
HFR None (permission denied)
Archive Read/Write