Systems Admin Reference

This page gives a reference to all membertility views which are available to members who have access to the Systems menu via various security roles.

Systems view

Navigation: Systems > Systems

The Systems view defines all of the systems members may need access to because of a position they hold. See Systems and Access Levels.

System:

name of the system, e.g., Google Workspace, MailChimp, Canva, the club website, a RunSignUp race, membertility itself, or any other system the club needs access to

Slug:

stable identifier for this system, used in place of its name in the bootstrap CSVs (bundles.csv, and the access-report --actual-csv) so a CSV keeps working even if the system’s name is later reworded. Must be unique. Recommended: lowercase, hyphenated, e.g. mailchimp, google-workspace

Description:

describes the system, possibly giving more information than just the name

Active:

if yes, this system is in current use

System Access Levels view

Navigation: Systems > System Access Levels

The System Access Levels view defines the levels of access available within each system. Every system needs at least one access level, even if there’s only one tier of access – see Systems and Access Levels.

System:

the system this access level belongs to

Access Level:

name of the access level, e.g. “Super Admin” for one of membertility’s several administrative security roles

Slug:

stable identifier for this access level, used in place of its name in the bootstrap CSVs. Must be unique within its system (but may repeat across different systems, e.g. two systems can each have an super-admin slug). Recommended: lowercase, hyphenated, e.g. super-admin

Description:

describes the access level, possibly giving more information than just the name

Active:

if yes, this access level is in current use

Access Types view

Navigation: Systems > Access Types

The Access Types view defines named bundles of system/access level pairs which are shared by several positions – see Access Types.

Access Type:

name of the access type, e.g. “Race Director access”

Slug:

stable identifier for this access type, used in place of its name in the bootstrap CSVs (bundles.csv, positions.csv). Must be unique. Recommended: lowercase, hyphenated, e.g. race-director-access

Description:

describes the access type, possibly giving more information than just the name

Active:

if yes, this access type is in current use

System Access:

the system/access level pairs bundled into this access type

Access Checklist view

Navigation: Systems > Access Checklist

The Access Checklist view lists system access grant/revoke actions a systems admin needs to take in the real external systems, generated automatically when a member’s positions change in a way that changes what access they need – see Access Checklist. Every field except Resolved is set automatically and can’t be edited.

Status:

Open while the entry is still outstanding, Resolved once Resolved below has been set

Member:

the member whose required access changed

Action:

grant if the member newly needs this access, revoke if they no longer need it

System:

the system this entry is about

Access Level:

the access level this entry is about

Position:

the position whose change triggered this entry

Effective Date:

date the change takes effect

Detected:

date and time this entry was added to the checklist

Resolved:

once the systems admin has made the actual change in the real system, edit this to today’s date to check the entry off the list. Leave blank while the entry is still outstanding.

Resolved By:

the member who resolved this entry, filled in automatically when Resolved is set

The view has the following filters:

Show resolved entries:

by default only unresolved entries are shown, since that’s the normal working view – check this to also see entries that have already been checked off

Member:

the member of interest

System:

the system of interest

Access Level:

the access level of interest

Position:

the position of interest