In this article we cover off the different types of security roles available in Fluid.
The access a user has to various capabilities and functionality in Fluid is related to the roles that are assigned to their account. To assign a user a role simply set the flag on the role from No to Yes on their account.
|Does the user need to be able to log into Fluid?|
This is the minimum role requirement for a user to be able to log into Fluid. User access provides general access to create, manage and participate in meetings, boards and teams.
|Project Related Roles|
|Does the user need access to the Fluid Projects module?|
This role is needed in order for the account to have access to the Fluid Projects module in Fluid.
|Does the user need READ access to ALL the projects in Fluid?|
Allows read access to ALL projects registered in Fluid. This role is typically reserved for relatively senior stakeholders who need complete transparency across the portfolio. Without Project Viewer access a person would need to be assigned a role on a project to be able to access it.
|Does the user need to be able to create new projects in Fluid?|
Only users with submission access can create new projects and/or programs from the universal CREATE button on the top navigation. Useful to restrict who can create and add new projects to the portfolio.
|Does the user need access to view and manage project financials?|
This roles gives the user access to the Financials sections of project workspaces, as well as any Financial reporting.
|Does the user need to approve project budgets?|
Fluid allows budget approval workflow. Only users with this role can approve project budget against projects.
|Is the user an accountable executive on projects?|
A person has to have the accountable executive role to be named as an accountable executive on a project.
|Does the user need access to view and manage project resourcing?|
Allows the user access to the Community (resourcing) section of project workspaces, as well as any Resource reporting
|Does the user need access to view and manage project benefits?|
This role gives the user access to the Benefits and Ongoing Costs sections of project workspaces, as well as any Benefits and Ongoing Costs reporting
|Timesheeting Roles - only relevant if timesheeting is enabled for the instance|
|Does the user manage a team?|
Team managers are able to manage, approve and report on their direct reports timesheets.
|Is the user exempt from having to submit timesheets?|
The user is not required to submit timesheets.
|Does the user need to create and manage user accounts in Fluid?|
Administrative rights to create and manage user accounts in Fluid.
|Does the user need READ/WRITE access to ALL the projects in Fluid?|
Full edit rights to all registered projects in Fluid.
|Does the user need access to manage/change the financial configuration settings and administer financials for ALL the projects in Fluid?|
Allows user access to the financial administration page to do bulk editing and the management of portfolio financial data - as well as make changes to finance related elements of the system configuration.
|Does the user need access to administer ALL the project information in Fluid?|
Access to the data administration page to do bulk download, edit and upload of project information and financials.
|Does the user need access to manage/change timesheet settings and administer ALL timesheets in Fluid?|
Access to edit timesheet settings, and manage the exempt user group and timesheet admin user group.
|Does the user need full administrator access to to manage/change all configuration settings and administer everything (projects, meetings, boards, teams) that is in Fluid?|
This role gives the user full administrator access to the entire Fluid instance to manage and administer system configuration and settings, data, financials, timesheeting and user accounts.
|An account with no roles associated to it is known as a 'ghost' account. Ghost accounts are used when a person needs to be represented in Fluid to be added to projects, meetings, boards for reporting purposes, but is not expected to access Fluid. Without any roles assigned to it an account cannot be used so these accounts are not licensed.|