---
title: "Security Manager Module"
canonical: "https://docs.rubiconwater.com/space/DMS/2018738333/Security%20Manager%20Module"
format: markdown
---
> ℹ️ **Where is this module?**
> ℹ️ 
> ℹ️ This module is usually in the **User Management** tab of the application

> Macro (excerpt)
> 
> Use the Security Manager module to view and manage authorities for parts of the application that logged-in users can see or use, including functions, scopes, modules and reports.

> Macro (pagetree)



# Why use the Security Manager?

If you are managing access to the application, these are the advantages of using the Security Manager:

- It is easier to locate authorities in the Security Manager because it displays only authorities for application related objects such as modules, functions, scopes, and reports.
- You can see both direct and inherited authorities for roles in the tree view of the **Security Manager > By Role** tab.
- You can configure whether or not an authority can be inherited from a sub-role.

# What’s the difference between functions and scopes?

Scopes are primarily used to control functionality in the newer NeuroFlo apps while functions control functionality in the original NeuroFlo desktop applications.

Scopes and functions both define specific behaviours that can be assigned to a user or a role. Unlike functions, scopes can also be assigned to specific applications to control what you can do in those applications, but this is not done in Security Manager and cannot be configured by end users.

So from the end user’s point of view they are effectively the same.

# Layout of the Security Manager Module