Page Comparison

{anchor:top}
{toc: class=contents}
h2. OverviewRole List
{styleclass: Class=topLink}[top|#top]{styleclass}
This section describes how roles are created and managed within Yellowfin.  Roles are allocated to users and define a set of functions that the user is permitted to access within Yellowfin.the 
h2. Role List
{styleclass: Class=topLink}[top|#top]{styleclass}
system. The role list is accessible via the administrationAdmin panelConsole.  As a default you will have a number of pre-configured roles.  These are listed below.

!132044roles.png!

 
h2. Sample Yellowfin Roles
{styleclass: Class=topLink}[top|#top]{styleclass}
When Yellowfin is initially deployed a standard set of roles is provided to you.  These are: 
||Administrator|The Yellowfin Administration role has access to database and user administration functions. These functions include managing users, groups and other configuration parameters.
It also has all the report writing and reading access supplied by the other roles below plus advanced functions, including:
SQL Reports, Public Publishing, Drill Through Reports, Discussion Admin Rights.|
||Public Writer|The Yellowfin Report Public writer has access for creating and editing Public reports.
All users that are to publish reports for Public use must have the Public Role to do so.
Reports created by a Yellowfin Public Writer can include drill through reports, multicast reports, and report emailing.| 
||Report Consumer|The Yellowfin Report Consumer can only read reports that have been published to the Public repository.
Access exists to favourites, a dashboard and report viewing.|
||Report Writer|The Yellowfin Report Writer has access to favourites, a dashboard and Private report creation. 
A Yellowfin report writer cannot produce reports with drill through, broadcast or MI capabilities.|

 
h2. Edit / Create Role
{styleclass: Class=topLink}[top|#top]{styleclass}
In #order Toto create or edit an existing role click either the create link or the role name that you wish to update.  This will open the role edit form.
# Provide your role with a meaningful name and description.  
!133.png!
# You can now choose to make this role a new role you will need complete the following:
# Click on the *Add* button located at the bottom of the Roles list in the Admin Console
# You will now be taken to the Role Details page and will need to define these components:
## Provide a meaningful Name and Description that outlines the purpose or use of the role
## Enable the role as Mandatory, Default, or Guest: as required. (Optional)
|*Mandatory*|This means that once this role has been created, and at least one user assigned the role, when users are deleted Yellowfin will check the role to ensure there is always at least one user with this role in the system. So if you try to delete the only user assigned the Mandatory role you will experience the following error:
!01mandatoryError.png!|
|*Default Role*|This means that when a user is created in Yellowfin, either by an Administrator, or through LDAP, they will be assigned this role unless otherwise specified|
|*Guest Role*|Guest roles are used for accessing external content.|
|*Tour Storyboard*|## Select an existing public storyboard to present to new users from the [Welcome|User Welcome] page.| #(Optional)
Tick## theEnable/Disable functions you wish to allocate to the user. as required. A description of each thesefunction is available by rollinghovering over the info icon on the reportright informationhand iconside. !134.png!
{color:#C00000}*Note:*{color} See _[Available Security Functions]_ for a full list.
#
## Define the CRUD permissions where required. Some functions will require you to provide the appropriate CRUD functionality.  have a C R U D checkbox list as part of the settings. The acronym CRUD refers to all of the major functions that need to be implemented.  Each letter in the acronym can be mapped to a standard SQL statement:
|*Create*|INSERT new records|
|*Read*|SELECT records from the database|
|*Update*|UPDATE records in the database|
|*Delete*|DELETE records in the database|
One example of CRUD access is for dashboards.  If a user only has R selected they will be able to read dashboard but not create new dashboard tabs or add reports to their tabs.  Whilst a user with CRUD will be able to create and delete dashboard tabs.
### The last option you have in the role settings is to specify what columns should be made available to users when viewing the report list. 
!135.png!
# Click Save when you have completed editing to make your role available. 
{color:#C00000}*Note:*{color} Yellowfin will do a function check to ensure you do not breach your license agreement.


h2. Edit/Copy Role
{styleclass: Class=topLink}[top|#top]{styleclass}

h2. Delete Role
{styleclass: Class=topLink}[top|#top]{styleclass}

\\
\\
{horizontalrule}
{styleclass: Class=topLink}[top|#top]{styleclass}