Super Admin Reference

Applications view

Navigation: Super > Applications

The Applications view has one entry per loutilities application. This should only be changed by the software development team.

Note

This data is in the common database. See Single Sign-On for details about how the common database is used.

Email Templates view

Navigation: Super > Email Templates

The Email Templates view has one entry per system email type. For details of the substitution variable usage, see the indicated software module(s).

email types and substitution variables

module	email type	substitution variables	software module(s)
leadership task	leader-email	members, member.tasks, task.task, task.expires	leadership_emails.py
leadership task	member-email	tasks, task.task, task.status, task.expires	leadership_emails.py

Files view

Navigation: Super Files

The Files view gives the superadmin visibility into the files which were uploaded into the system.

Interests view

Navigation: Super > Interests

The Interests view gives the superadmin control over what interests are available to what applications, and to control what users/members are able to access what interests (the latter is also available via the Members view).

Note

This data is in the common database. See Single Sign-On for details about how the common database is used.

Description

name of interest, used for the select in the banner in all the views

Slug

used to identify the interest in URLs

Public

yes or no for whether this interest is visible via the public interface

Applications

applications within which this interest is shown

Users

users/members who are able to use this interest

Interest Attributes view

Navigation: Super > Interest Attributes

The Interest Attributes view allows the superadmin to control certain attributes which may be specified by interest.

Note

This data is in the local application database.

Interest

this view is pre-populated with interests which are defined in the Interests view

Initial Expiration

Expiration Date to be used for tasks which have Period defined and have not ever been marked complete

From Email

email address to be used as the from address for emails sent by the system

Roles view

Navigation: Super > Roles

The Roles view is used to define security roles and assign them to specific applications. This must be coordinated with the software developement and is therefore best left to the software development team to configure.

Name

name of the security role, as used by the application internally

Description

description of the security role, i.e., what it means to the user/member system capabilities

Applications

applications which use this security role

Note

This data is in the common database. See Single Sign-On for details about how the common database is used.