Portal Redirects
As you replace your Portal pages with widgets or other pages on your website, can you be sure you replaced all the links?
If you think it's possible you could have missed some, or just to be thorough, we recommend setting up automatic Portal redirects. That way, once the Portal goes away, those links will take your congregants to the correct page on your website.
You can redirect all Portal pages to one location on your website, or redirect each Portal page to a specific link.
How Does It Work?
If someone attempts to access a Portal page that you've set up a redirect for, they are first taken to an informative webpage. They'll see "The page [page name] has moved:" along with "You will now be redirected to [redirect link]". They are automatically redirected to that link after 10 seconds, or they can click the hyperlink to immediately access the redirect page you set up.
Redirect All Portal Pages to One Location
Set a global link to override all Portal pages and point congregants to one location on your website.
- In the navigation menu, click .
- Search for Application Code "PORTAL" and List Name "sunset_redirects".
- Locate the Key Name "global".
- If you find it, open it and click Edit Record.
- If you don't find it, click New Configuration List to add the record.
- For Value, enter the fully qualified URL for the page on your website that you want to direct congregants to. For example, "https://example-church.com/welcome".
- Click Save.
The changes should take effect within 10 minutes. If needed, you can force a reload using portal/login.aspx?reloadPortalSettings=true.
Redirect Individual Portal Pages
Set specific links to override individual Portal pages and point congregants to the relevant location on your website.
The changes should take effect within 10 minutes. If needed, you can force a reload using portal/login.aspx?reloadPortalSettings=true.
Individual Portal Redirect Key Names
These are the available Portal configuration setting key names that can redirect your congregants to a relevant page on your website.
- backgroundcheck
- Permanent redirect away from the Background Check page in the Portal. This can link to the place on your website where you send contacts who need to complete a background check. Or, you can link to your background check integration partner's site. For more on that, see Background Check Request Tool.
- create_account
- Permanent redirect away from the page in the Portal where users can create an account. This can link to the place on your website where contacts create an account, such as the Login widget.
Example: "https://example-church.minstryplatform.net/ministryplatformapi/oauth/create"
- edit_group_meeting
- Permanent redirect away from the page in the Portal where users can edit a group meeting.
Example, if leaders are using Group Life: "https://example-church.cloudapps.ministryplatform.cloud/apps/grouplife/{group}"
- edit_group_member
- Permanent redirect away from the page in the Portal where users can edit a group member.
- event_calendar
- Permanent redirect away from the Event Calendar page in the Portal. This can link to the place on your website where users view events, such as the Event Finder widget. If you plan to redirect Event Details, we recommend setting this value so that saved links and search engines will direct to your new location.
Example: "https://example-church.com/events"
- event_detail
- Permanent redirect away from the Event Detail page in the Portal, including the record ID in the query string. This can link to the place on your website where users view details about an event, such as the Event Detail & Registration widget. If you're not ready to move to the Event Finder widget, you can redirect just the events themselves to your Event Details widget. We recommend setting this value so that saved links and search engines will direct to your new location.
Example: "https://example-church.com/event-details/?id={id}"
- event_signup
- Permanent redirect away from the page in the Portal where users can sign up for an event. This can link to the place on your website where users register for an event, such as the Event Detail & Registration widget.
Example: "https://example-church.com/event-details/?id={id}"
- get_form
- Permanent redirect away from the Forms page in the Portal. This can link to a custom form.
Example: "https://example-church.com/forms/?id=" plus the Form GUIID from the Form record
- group_detail
- Permanent redirect away from the Group Detail page in the Portal, including the record ID in the query string. This can link to the place on your website where users view details about a group, such as the Group Detail widget.
Example: "https://example-church.com/group-details/?id={id}"
- group_finder
- Permanent redirect away from the Group Finder page in the Portal. This can link to the place on your website where users view available groups, such as the Group Finder widget.
Example: "https://example-church.com/groups"
- group_signup
- Permanent redirect away from the page in the Portal where users can sign up for a group. This can link to the place on your website where users request to join a group, such as the Group Detail widget.
Example: "https://example-church.com/group-details/?id={id}"
- group_survey
- Permanent redirect away from the Group Finder by Survey page in the Portal. This can link to the place on your website where users filter to locate groups, such as the Group Finder widget.
- make_a_pledge
- Permanent redirect away from the Make A Pledge page in the Portal, including the record ID in the query string if applicable. This can link to the place on your website where users pledge toward a campaign, such as the Make a Pledge widget.
Example: "https://example-church.com/pledge/?id={id}"
- mission_trip_giving
- Redirect away from the Mission Trip Giving page in the Portal. This can link to the place on your website where users give financially toward others participating in mission trips. This replaces {ogo-token}, if you've set that up.
Example: "https://example-church.com/mission-trips"
- mission_trip_registration
- Permanent redirect away from the Mission Trip Registration page in the Portal. Query string [missionTripId] will be transferred to [id] if applicable.
Example: "https://example-church.com/mission-trips/?id={id}"
- mission_trips
- Permanent Redirect away from the Mission Trips page in the Portal. This can link to the place on your website where users view mission trips, such as the Mission Trip Application widget.
Example: "https://example-church.com/mission-trips"
- my_calls
- Permanent redirect away from the My Calls page in the Portal. This can link to the place on your website where users view and manage phone calls assigned to them.
Example: "https://example-church.com/my-calls"
- my_contribution_statement
- Permanent redirect away from the My Contribution Statement page in the Portal. This can link to the place on your website where users view their statements, such as the My Contribution Statements widget.
Example: "https://example-church.com/my-statements"
- my_directory
- Permanent redirect away from the Online Directory page in the Portal. This can link to the place on your website where authenticated users view basic information about fellow congregants or parishioners, such as the Online Directory widget.
Example: "https://example-church.com/directory"
- my_events
- Permanent redirect away from the My Events page in the Portal. This can link to the place on your website where users view the events they showed interest in or have registered for, such as the My Invoices widget.
Example: "https://example-church.com/my-events"
- my_giving
- Permanent redirect away from the My Giving page in the Portal. This can link to the place on your website where users view their financial gifts, such as the My Giving widget. We recommend setting this value so that saved links and search engines will direct to your new location.
Example: "https://example-church.com/my-giving"
- my_groups
- Permanent redirect away from the My Groups page in the Portal. This can link to the place on your website where users view the groups they are part of, such as the My Groups widget.
Example, if participants are using Group Life: "https://example-church.cloudapps.ministryplatform.cloud/apps/grouplife"
- my_group_detail
- Permanent redirect away from the My Group Detail page in the Portal, including the record ID in the query string. This can link to the place on your website where users view details about the groups they are part of, such as the Group Detail widget.
Example, if participants are using Group Life: "https://example-church.cloudapps.ministryplatform.cloud/apps/grouplife/{group}"
- my_group_meeting
- Permanent redirect away from the page in the Portal where users can view their group meeting. This can link to the place on your website where users view meetings for the groups they are part of, or link to Group Life.
- my_group_members
- Permanent redirect away from the page in the Portal where users can view their group members. This can link to the place on your website where users view other members for the groups they are part of, or link to Group Life.
- my_group_message
- Permanent redirect away from the page in the Portal where users can view their group messages. This can link to the place on your website where users view messages for the groups they are part of, or link to Group Life.
- my_group_suggestion
- Permanent redirect away from the page in the Portal where users can suggest a group. This can link to the place on your website where users suggest ideas for new groups, such as the Group Finder widget.
Example: "https://example-church.com/groups/suggestions"
- my_mission_trips
- Permanent redirect away from the My Mission Trips page in the Portal. This can link to the place on your website where users view and manage their mission trips, such as the My Mission Trips widget.
Example: "https://example-church.com/my-mission-trips"
- my_mission_trip_detail
- Permanent redirect away from the My Mission Trip Detail page in the Portal, including the record ID in the query string. This can link to the place on your website where users view details about a mission trip they are part of, such as the My Mission Trips widget.
Example: "https://example-church.com/my-mission-trips/?id={id}"
- my_pledges
- Permanent redirect away from the My Pledges page in the Portal. This can link to the place on your website where users view their pledge progress, such as the My Pledges widget.
Example: "https://example-church.com/my-pledges"
- my_profile
- Permanent redirect away from the My Profile page in the Portal. This can link to the place on your website where authenticated users indicate attributes that describe themselves, such as the About Me widget.
Example: "https://example-church.com/about-me"
- my_purchase_history
- Permanent redirect away from the My Purchase History page in the Portal. This can link to the place on your website where authenticated users view invoices for event registrations, such as the My Invoices widget.
Example: "https://example-church.com/my-invoices"
- my_subscriptions
- Permanent redirect away from the My Subscriptions page in the Portal. This can link to the place on your website where users view and update their publication subscriptions, such as the My Subscriptions widget, the One-Click Unsubscibe widget, or the Subscribe to Publication widget.
Example: "https://example-church.com/my-subscriptions"
- my_user_account
- Permanent redirect away from the My User Account page in the Portal. This can link to the place on your website where users update their own information, such as the Login widget or the My Household widget.
Example: "https://example-church.minstryplatform.net/ministryplatformapi/oauth/?profile"
- online_giving
- Redirect away from the Online Giving page in the Portal. This can link to the place on your website where people give financially toward your church via a one-time donation. This replaces {ogo-token}, if you've set that up.
Example: "https://example-church.com/give"
- opportunity_detail
- Permanent redirect away from the Opportunity Detail page in the Portal, including the record ID in the query string. This can link to the place on your website where users view details about available opportunities, such as the Opportunity Detail widget.
Example: "https://example-church.com/opportunities/?id={id}"
- opportunity_finder
- Permanent redirect away from the Opportunity Finder page in the Portal. This can link to the place on your website where users view available opportunities, such as the Opportunity Finder widget.
Example: "https://example-church.com/opportunities"
- opportunity_survey
- Permanent redirect away from the Opportunity Finder by Survey page in the Portal. This can link to the place on your website where users filter to locate opportunities, such as the Opportunity Finder widget.
- transaction_summary
- Permanent redirect away from the Transaction Summary (Checkout) page in the Portal. This can link to the place on your website where users complete payments for events, such as the My Invoices widget. We recommend setting this value so that saved links and search engines will direct to your new location.
Example: "https://example-church.com/checkout"