Core Docs - Engagement - Edit Step Programs

Rock Version: v19.0
Last Modified: 2026-03-25 12:02 PM

Let’s go back to the Step Program page to see how we can edit our programs. Clicking the Edit button lets you update the program and its configurable settings.

Default List View

Steps information for an individual can be viewed under the Steps tab on the person profile, either as cards or in a grid. You can toggle between these views from within the person profile using the ti ti-grid-dots and ti ti-list buttons. As noted in the prior section, the default view is set at the step program level.

The screenshots above (cards) and below (grid) are both for the same person following the Discipleship program.

While in card view, hovering over a card lets you view additional details as well as access the Step Entry page. This is controlled by the Step Type Advanced Settings (see Editing Step Types).

Step Security
A person needs to be in a role with Edit permission for the Steps block in order to add steps from the Person Profile page.  

Cards or Grid?
The cards view will condense multiple occurrences of a step into a single card, whereas the grid view will display a row for every occurrence of the step. For this reason, the grid view may be more appropriate for step programs that allow steps to be repeated often. The grid view also displays a "Summary" column that shows step attributes configured to show on grids.

If you have multiple campuses, you can choose to show or hide the campus associated with a step by changing this block's settings. This applies to both the cards and grid views.

The default view doesn't have to be the same for all of your programs. Choose the one that seems best for each individual program. You can always change it later if you need to.

Statuses

The values you set up here are used to track an individual’s status for any step type in the program. This list shows each status and whether it is treated as Completing the step.

The Create Status page is used when adding or changing a status.

Completed But Not Completed
In the Step Entry section we discussed the “Date Completed” field. It’s important to note that this date, by itself, is not enough to indicate that the person has finished a step. For a person to truly complete a step, an “Is Complete” status and a completion date should both be present.  

Entity Attributes

If you have an Entity Attribute configured for Step Programs, it will appear in the settings here.

Using Entity Attributes for Step Programs lets you apply attributes across all programs. In this example, Internal Program is a Boolean that can be selected for any Step Program. This works well for attributes you need system-wide.

To add a new attribute for this program, go to Admin Tools > Settings > Entity Attributes and select Step Program as the Entity Type.

Workflows

Here you can add one or more workflows to the program. Keep in mind that workflows added to the program apply to all the steps in program, regardless of the step type.

The workflow can be launched according to one of three triggers:

See our Workflows guide for more information on creating workflows.

Why Use Step Program Workflows?
Applying a workflow at the step program level (as opposed to the step type level, described in the next section) is a great way to save yourself time and effort on repetitive tasks. For example, do you have an email that should be sent after the completion of each step in a program? If so, it can be added and maintained once at the program level instead of individually for each step type.