Difference between revisions of "Security"

From BudgetLink Wiki
Jump to navigation Jump to search
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Overview ==
== Overview ==


BudgetLink's security feature allows you to control:
BudgetLink's security feature allows you to control who can use the software, what jobs users can report on, what reports are available and if budgets can be edited.
* who can use the software;
 
* what jobs users can report on;
It is particularly useful in the following situations:
* what reports are available;
* Allowing users to run reports for their department without given them access to the full data file;
* if budgets can be edited.
* Allowing users to run reports only against the [[Jobs]], [[Classess]] or [[Tracking Categories]] that fall within their role;
* Controlling which users can view different sets of reports.


== How to Guides ==
== How to Guides ==
Line 11: Line 12:
=== Managing security logins ===
=== Managing security logins ===


BudgetLink has the capability to restrict which users can use the software. For more information see [[Managing Security Logins]].
BudgetLink has the capability to restrict which users can use the software. For more information, see [[Adding a login]], [[Renaming a login]], [[Changing the password of a login]] or [[Removing a login]].


=== Restricting the jobs to which users have access ===
=== Restricting the jobs to which users have access ===


BudgetLink has the capability, through the security logins, to restrict the jobs to which a user has access. For more information see [[Restricting the jobs to which users have access]].
BudgetLink has the capability, through the security logins and [[Job Sets|job sets]], to restrict the jobs to which a user has access. For more information, see [[Restricting the jobs to which users have access]].


=== Restricting the reports to which users have access ===
=== Restricting the reports to which users have access ===


BudgetLink has the capability, through the security logins, to restrict the reports to which a user has access. For more information see [[Restricting the reports to which users have access]].
BudgetLink has the capability, through the security logins and [[Worksheet Sets|worksheet sets]], to restrict the reports to which a user has access. For more information, see [[Restricting the reports to which users have access]].


=== Locking budgets ===
=== Locking budgets ===


BudgetLink has the capability, through [[Version Control]], to prevent budgets from being edited. For more information see [[Locking Budgets]].
BudgetLink has the capability, through [[Version Control]], to prevent budgets from being edited. For more information, see [[Locking Budgets]].

Latest revision as of 20:39, 5 September 2013

Overview

BudgetLink's security feature allows you to control who can use the software, what jobs users can report on, what reports are available and if budgets can be edited.

It is particularly useful in the following situations:

  • Allowing users to run reports for their department without given them access to the full data file;
  • Allowing users to run reports only against the Jobs, Classess or Tracking Categories that fall within their role;
  • Controlling which users can view different sets of reports.

How to Guides

Managing security logins

BudgetLink has the capability to restrict which users can use the software. For more information, see Adding a login, Renaming a login, Changing the password of a login or Removing a login.

Restricting the jobs to which users have access

BudgetLink has the capability, through the security logins and job sets, to restrict the jobs to which a user has access. For more information, see Restricting the jobs to which users have access.

Restricting the reports to which users have access

BudgetLink has the capability, through the security logins and worksheet sets, to restrict the reports to which a user has access. For more information, see Restricting the reports to which users have access.

Locking budgets

BudgetLink has the capability, through Version Control, to prevent budgets from being edited. For more information, see Locking Budgets.