Core Features

A deeper dive into some of the application basics.

Table of Contents
  1. Navigation
  2. Systems
  3. User
  4. Privacy



Systems

"Systems" are the core functional input needed for SAGE to work. A system is simply a representation of a single STEP environment that you add to SAGE, telling the application where to connect.

If you work with STEP, you likely manage multiple environments like sandboxes, development, testing, and production instances. Each of these is a 'System' in SAGE.

You can navigate to the Systems Page and add each system you work with using the 'Add System' button.

In the form that opens up, fill in the details. Every field shown is mandatory:

Add System Form

You can add multiple systems and switch between them by selecting any one from the Systems Page using the 'toggle' button at the top right of the card. The selected system will be highlighted with a colored background.

You can also edit an existing added system by clicking the edit button or delete it, as needed.

Multiple Systems


User

Access to SAGE's features is locked behind a user account. This allows multiple people to use the application and have their own set of stored data (like configured systems).

To create a user account, click on the 'Register' button. It's visible in the homepage or in the User Details panel. Fill in the form to have an account created.

Once registered, you can log in with your credentials and proceed to add and manage your Systems.

There is a special 'Admin' role that is automatically granted to the first user who registers on the system. This role comes with additional options, allowing the admin to monitor SAGE usage and manage application settings.



Privacy

SAGE is designed as a helper application. No analytics or data from your STEP system are collected, with the exception of a few functional data points. And NONE of those are shared with any third party.

These data points are:

  1. The time when a user was last active for Admin auditing
  2. The number of visits to a particular page per user. This helps to gauge which features are used most, guiding future development.
  3. The system details fetched on the homepage, along with the data you input when adding a system, are saved in the database. This is solely to provide convenience to the user; this data is not being used in any other way.